From: Yu Kuai <yukuai@fnnas.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, linux-raid@vger.kernel.org,
Song Liu <song@kernel.org>, Li Nan <linan122@huawei.com>,
Xiao Ni <xiao@kernel.org>,
Abd-Alrhman Masalkhi <abd.masalkhi@gmail.com>,
Benjamin Marzinski <bmarzins@redhat.com>,
Junrui Luo <moonafterrain@outlook.com>,
Keith Busch <kbusch@kernel.org>
Subject: [GIT PULL] md-7.1-20260428
Date: Tue, 28 Apr 2026 22:33:40 +0800 [thread overview]
Message-ID: <20260428143340.1088943-1-yukuai@fnnas.com> (raw)
Hi Jens,
Please consider pulling the following changes into your block-7.1
branch.
This pull request contains:
Bug Fixes:
- Fix a raid5 UAF on IO across the reshape position.
- Avoid failing RAID1/RAID10 devices for invalid IO errors.
- Fix RAID10 divide-by-zero when far_copies is zero.
- Restore bitmap grow through sysfs.
Cleanups:
- Use mddev_is_dm() instead of open-coding gendisk checks.
- Use ATTRIBUTE_GROUPS() for md default sysfs attributes.
- Replace open-coded wait loops with wait_event helpers.
Others:
- Add Xiao Ni as md/raid reviewer.
Thanks,
Kuai
---
The following changes since commit 0898a817621a2f0cddca8122d9b974003fe5036d:
cdrom, scsi: sr: propagate read-only status to block layer via set_disk_ro() (2026-04-27 15:52:51 -0600)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/mdraid/linux.git tags/md-7.1-20260428
for you to fetch changes up to 3b2f70eab5a2cd15e27b1447e66e45302b28ff2c:
md: use ATTRIBUTE_GROUPS() for md default sysfs attributes (2026-04-28 20:44:38 +0800)
----------------------------------------------------------------
Abd-Alrhman Masalkhi (5):
md: replace wait loop with wait_event() in md_handle_request()
md: use mddev_lock_nointr() in mddev_suspend_and_lock_nointr()
md/raid1: replace wait loop with wait_event_idle() in raid1_write_request()
md: use mddev_is_dm() instead of open-coding gendisk checks
md: use ATTRIBUTE_GROUPS() for md default sysfs attributes
Benjamin Marzinski (1):
md/raid5: Fix UAF on IO across the reshape position
Junrui Luo (1):
md/raid10: fix divide-by-zero in setup_geo() with zero far_copies
Keith Busch (1):
md/raid1,raid10: don't fail devices for invalid IO errors
Xiao Ni (1):
MAINTAINERS: Add Xiao Ni as md/raid reviewer
Yu Kuai (3):
md: factor bitmap creation away from sysfs handling
md/md-bitmap: split bitmap sysfs groups
md/md-bitmap: add a none backend for bitmap grow
MAINTAINERS | 1 +
drivers/md/md-bitmap.c | 131 ++++++++++++++++++++++++++++++----
drivers/md/md-bitmap.h | 2 +-
drivers/md/md-llbitmap.c | 7 +-
drivers/md/md.c | 182 ++++++++++++++++++++++++++---------------------
drivers/md/md.h | 6 +-
drivers/md/raid1-10.c | 7 +-
drivers/md/raid1.c | 15 ++--
drivers/md/raid10.c | 2 +
drivers/md/raid5.c | 7 +-
10 files changed, 251 insertions(+), 109 deletions(-)
next reply other threads:[~2026-04-28 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 14:33 Yu Kuai [this message]
2026-04-28 14:41 ` [GIT PULL] md-7.1-20260428 Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260428143340.1088943-1-yukuai@fnnas.com \
--to=yukuai@fnnas.com \
--cc=abd.masalkhi@gmail.com \
--cc=axboe@kernel.dk \
--cc=bmarzins@redhat.com \
--cc=kbusch@kernel.org \
--cc=linan122@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=moonafterrain@outlook.com \
--cc=song@kernel.org \
--cc=xiao@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox