From: Jens Axboe <axboe@kernel.dk>
To: Yu Kuai <yukuai@fnnas.com>
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: Re: [GIT PULL] md-7.1-20260428
Date: Tue, 28 Apr 2026 08:41:53 -0600 [thread overview]
Message-ID: <982f5bcc-8caf-465d-99c7-3b457cab20c7@kernel.dk> (raw)
In-Reply-To: <20260428143340.1088943-1-yukuai@fnnas.com>
On 4/28/26 8:33 AM, Yu Kuai wrote:
> 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.
Two notes:
1) Why are you rebasing the tree right before sending it? There
should be zero need to do that, please don't.
2) Please switch to https://patch.msgid.link/ for you Link tags,
if they are just links to the patch submission. That makes it
clear this is the case, just the patch. You can use lore for
actual bug reports etc.
Pulled, but please change the above two things going forward.
--
Jens Axboe
prev parent reply other threads:[~2026-04-28 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 14:33 [GIT PULL] md-7.1-20260428 Yu Kuai
2026-04-28 14:41 ` Jens Axboe [this message]
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=982f5bcc-8caf-465d-99c7-3b457cab20c7@kernel.dk \
--to=axboe@kernel.dk \
--cc=abd.masalkhi@gmail.com \
--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 \
--cc=yukuai@fnnas.com \
/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