From: Sagi Grimberg <sagi@grimberg.me>
To: mengfanhui <mengfanhui@kylinos.cn>, Christoph Hellwig <hch@lst.de>
Cc: kbusch@kernel.org, axboe@kernel.dk, linux-kernel@vger.kernel.org,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme-multipath: fix bogus request queue reference put
Date: Wed, 20 Mar 2024 11:06:31 +0200 [thread overview]
Message-ID: <a1ebff42-4ddb-4e17-978c-2f02106a9d90@grimberg.me> (raw)
In-Reply-To: <4b9e1f54-9032-48b6-bfbb-d47a4b7857e3@kylinos.cn>
On 20/03/2024 4:03, mengfanhui wrote:
> In this scenario. upstream should also appear.
I'd be surprised if it is,
The proposed patch was superseded by:
f165fb89b71f ("nvme-multipath: convert to blk_alloc_disk/blk_cleanup_disk")
Please verify that this exists upstream.
prev parent reply other threads:[~2024-03-20 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 6:50 mengfanhui
2024-01-17 14:04 ` Sagi Grimberg
2024-01-17 14:39 ` Christoph Hellwig
2024-03-14 6:13 ` mengfanhui
2024-03-17 7:33 ` Sagi Grimberg
2024-03-20 2:03 ` mengfanhui
2024-03-20 9:06 ` Sagi Grimberg [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=a1ebff42-4ddb-4e17-978c-2f02106a9d90@grimberg.me \
--to=sagi@grimberg.me \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mengfanhui@kylinos.cn \
/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®