From: Keith Busch <kbusch@kernel.org>
To: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>,
Nilay Shroff <nilay@linux.ibm.com>,
Hannes Reinecke <hare@suse.de>,
Qiliang Yuan <qiliang.yuan@linux.dev>
Cc: <linux-nvme@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
Hannes Reinecke <hare@kernel.org>
Subject: Re: [PATCH v6 0/3] nvme-multipath: requeue work fixes
Date: Fri, 20 Nov 2026 11:54:24 -0800 [thread overview]
Message-ID: <179520446477.200156.16466129687568880255.b4-ty@kernel.org> (raw)
In-Reply-To: <20261119-bug-nvme-mpath-set-live-srcu-v6-0-da85b18b274b@linux.dev>
On Thu, 19 Nov 2026 20:25:00 -0500, Qiliang Yuan wrote:
> Patch 1 keeps a large delayed_removal_secs from wrapping around into a
> short delay when it is converted to jiffies.
>
> Patch 2 applies a new delayed_removal_secs to a head removal that is
> already pending, so that clearing it fails the I/O queued without a
> usable path right away instead of when the old delay expires.
>
> [...]
Thanks, applied to nvme-7.4.
[1/3] nvme-multipath: keep a large delayed_removal_secs from wrapping around
commit: a280772ee0a8a1f2ac769be4d88a5c52ef5ed743
[2/3] nvme-multipath: apply delayed_removal_secs changes to a pending removal
commit: 536a72ea54f81ebdf56a2a0b31d7dc0fb2837c1d
[3/3] nvme-multipath: don't wait for a grace period in nvme_mpath_set_live()
commit: 3ca1ccf527aae210ecee2905062dd6da0934416a
--
Keith Busch <kbusch@kernel.org>
prev parent reply other threads:[~2026-11-20 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 1:25 Qiliang Yuan
2026-11-20 1:25 ` [PATCH v6 1/3] nvme-multipath: keep a large delayed_removal_secs from wrapping around Qiliang Yuan
2026-11-20 17:35 ` Nilay Shroff
2026-11-20 1:25 ` [PATCH v6 2/3] nvme-multipath: apply delayed_removal_secs changes to a pending removal Qiliang Yuan
2026-11-20 1:25 ` [PATCH v6 3/3] nvme-multipath: don't wait for a grace period in nvme_mpath_set_live() Qiliang Yuan
2026-11-20 19:54 ` Keith Busch [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=179520446477.200156.16466129687568880255.b4-ty@kernel.org \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hare@kernel.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nilay@linux.ibm.com \
--cc=qiliang.yuan@linux.dev \
--cc=sagi@grimberg.me \
/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
all inboxes | Powered by JetHome®