diff options
| author | Christian Brauner <brauner@kernel.org> | 2026-07-23 11:26:28 +0200 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2026-07-23 11:26:28 +0200 |
| commit | 1c9cb1826bd51bd74ee05adf5199065d83d400ec (patch) | |
| tree | 88e79fe35d1022e2aa3e4e2723c1f5ed0b838dd9 /rust/zerocopy-derive/git@git.tavy.me:linux.git | |
| parent | 503d67fbaec6fdeaba391cb497675071db9d16ea (diff) | |
| parent | 09b53b0787ee80b71b1dcceb99d004a33e55b823 (diff) | |
Merge patch series "iomap: trivial fixes for ext4 conversion"
Zhang Yi <yi.zhang@huaweicloud.com> says:
This patch series contains a few trivial iomap-related fixes in
preparation for converting ext4 buffered I/O to use iomap.
The first three patches are taken from my ext4 conversion series [1], as
suggested by Christoph. The fourth patch fixes a bug originally reported
by Sashiko during review of my series; although unrelated to the ext4
conversion, it is worth fixing on its own. Please see the following
patches for detail. The fifth patch add comments for
ifs_clear/set_range_dirty(), and the last patch avoids merging ioends
that have different private data.
[1] https://lore.kernel.org/linux-ext4/20260511072344.191271-1-yi.zhang@huaweicloud.com/
* patches from https://patch.msgid.link/20260714082325.325163-1-yi.zhang@huaweicloud.com:
iomap: add comments for ifs_clear/set_range_dirty()
iomap: fix out-of-bounds bitmap_set() with zero-length range
iomap: fix incorrect did_zero setting in iomap_zero_iter()
iomap: support invalidating partial folios
iomap: correct the range of a partial dirty clear
Link: https://patch.msgid.link/20260714082325.325163-1-yi.zhang@huaweicloud.com
Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
Diffstat (limited to 'rust/zerocopy-derive/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions
