From: Song Liu <songliubraving@meta.com>
To: Jens Axboe <axboe@kernel.dk>,
linux-raid <linux-raid@vger.kernel.org>,
"dm-devel@lists.linux.dev" <dm-devel@lists.linux.dev>
Cc: Mikulas Patocka <mpatocka@redhat.com>,
Yu Kuai <yukuai1@huaweicloud.com>, Li Nan <linan122@huawei.com>,
Yu Kuai <yukuai3@huawei.com>, Xiao Ni <xni@redhat.com>,
Benjamin Marzinski <bmarzins@redhat.com>
Subject: [GIT PULL] md-6.8 20240216
Date: Fri, 16 Feb 2024 20:13:01 +0000 [thread overview]
Message-ID: <2D753D1A-F9A6-4196-88A3-91C7596C17DD@fb.com> (raw)
Hi Jens,
Please consider pulling the following fixes for md-6.8 on top of your
block-6.8 branch. The major changes in this set are:
1. Fix issues reported for dm-raid [1], by Yu Kuai. Please note that
this PR only contains the first half of the set [2]. We still need
more fixes in dm and md code (the rest of the set, or alternative
fixes).
2. Fix active_io leak, by Yu Kuai. The fix was posted in the same set
[2]. But it actually fixes a separate issue [3].
I still hope to ship another fix for 6.8, which is discussed in [4], and
fixes bugzilla report [5]. For this fix, I would like to get review/ack
from Yu Kuai and Li Nan. We will get this one queued ASAP.
Thanks,
Song
[1] https://lore.kernel.org/linux-raid/e5e8afe2-e9a8-49a2-5ab0-958d4065c55e@redhat.com/
[2] https://lore.kernel.org/linux-raid/20240201092559.910982-1-yukuai1@huaweicloud.com/
[3] https://lore.kernel.org/linux-raid/20240130172524.0000417b@linux.intel.com/
Note that this specific email is talking about a different issue
than the rest of the thread.
[4] https://lore.kernel.org/linux-raid/20240207092756.2087888-1-linan666@huaweicloud.com/
[5] https://bugzilla.kernel.org/show_bug.cgi?id=218459
The following changes since commit 9f3fe29d77ef4e7f7cb5c4c8c59f6dc373e57e78:
md: fix a suspicious RCU usage warning (2024-01-24 22:58:00 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git tags/md-6.8-20240216
for you to fetch changes up to 9e46c70e829bddc24e04f963471e9983a11598b7:
md: Don't suspend the array for interrupted reshape (2024-02-15 14:17:27 -0800)
----------------------------------------------------------------
Yu Kuai (6):
md: Fix missing release of 'active_io' for flush
md: Don't ignore suspended array in md_check_recovery()
md: Don't ignore read-only array in md_check_recovery()
md: Make sure md_do_sync() will set MD_RECOVERY_DONE
md: Don't register sync_thread for reshape directly
md: Don't suspend the array for interrupted reshape
drivers/md/md.c | 70 ++++++++++++++++++++++++++++++++++++++++++++--------------------------
drivers/md/raid10.c | 16 ++--------------
drivers/md/raid5.c | 29 ++---------------------------
3 files changed, 48 insertions(+), 67 deletions(-)
next reply other threads:[~2024-02-16 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 20:13 Song Liu [this message]
2024-02-16 22:43 ` [GIT PULL] md-6.8 20240216 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=2D753D1A-F9A6-4196-88A3-91C7596C17DD@fb.com \
--to=songliubraving@meta.com \
--cc=axboe@kernel.dk \
--cc=bmarzins@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=linan122@huawei.com \
--cc=linux-raid@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=xni@redhat.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).