wireguard-linux/fs/bcachefs/io_write.h, branch update-toolchainWireGuard for the Linux kernelhttps://git.zx2c4.com/wireguard-linux/atom/fs/bcachefs/io_write.h?h=update-toolchain2024-07-14T23:59:12Zbcachefs: Rename BCH_WRITE_DONE -> BCH_WRITE_SUBMITTED2024-07-14T23:59:12ZKent Overstreetkent.overstreet@linux.dev2023-08-28T20:13:18Zurn:sha1:ae469056313f7d8a63646de8ef53eebfefc2d9c0
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
closures: CLOSURE_CALLBACK() to fix type punning2023-11-24T05:29:58ZKent Overstreetkent.overstreet@linux.dev2023-11-18T00:13:27Zurn:sha1:d4e3b928ab487a8aecd1f6a140b40ac365116cfb
Control flow integrity is now checking that type signatures match on
indirect function calls. That breaks closures, which embed a work_struct
in a closure in such a way that a closure_fn may also be used as a
workqueue fn by the underlying closure code.
So we have to change closure fns to take a work_struct as their
argument - but that results in a loss of clarity, as closure fns have
different semantics from normal workqueue functions (they run owning a
ref on the closure, which must be released with continue_at() or
closure_return()).
Thus, this patc introduces CLOSURE_CALLBACK() and closure_type() macros
as suggested by Kees, to smooth things over a bit.
Suggested-by: Kees Cook <keescook@chromium.org>
Cc: Coly Li <colyli@suse.de>
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Break up io.c2023-10-22T21:10:12ZKent Overstreetkent.overstreet@linux.dev2023-09-10T22:05:17Zurn:sha1:1809b8cba756d32bd6e976ed4ee64efdf66c6d94
More reorganization, this splits up io.c into
- io_read.c
- io_misc.c - fallocate, fpunch, truncate
- io_write.c
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>