From: Christoph Hellwig <hch@lst.de>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Greg KH <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH stable/5.4..5.8] nvme-mpath: replace direct_make_request with generic_make_request
Date: Wed, 7 Apr 2021 07:28:06 +0200 [thread overview]
Message-ID: <20210407052806.GA18573@lst.de> (raw)
In-Reply-To: <00e36c71-9f2c-5b38-96fd-3d471382f6ac@grimberg.me>
On Tue, Apr 06, 2021 at 06:04:09PM -0700, Sagi Grimberg wrote:
>
>>> Hence, we need to fix all the kernels that were before submit_bio_noacct was
>>> introduced.
>>
>> Why can we not just add submit_bio_noacct to the 5.4 kernel to correct
>> this? What commit id is that?
>
> Hey Greg,
>
> submit_bio_noacct was applied as part of a rework by Christoph that I
> didn't feel was suitable as a stable candidate. The commit-id is:
> ed00aabd5eb9fb44d6aff1173234a2e911b9fead
submit_bio_noacct really is just a new name for generic_make_request,
as the old one was horribly misleading. So this does use
submit_bio_noacct, just with its old name.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-04-07 5:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 20:08 [PATCH stable/5.4..5.8] nvme-mpath: replace direct_make_request with generic_make_request Sagi Grimberg
2021-04-03 6:10 ` Greg KH
2021-04-07 1:04 ` Sagi Grimberg
2021-04-07 5:28 ` Christoph Hellwig [this message]
2021-04-07 23:18 ` Sagi Grimberg
2021-04-09 9:43 ` Greg KH
2021-04-09 9:33 ` Patch "nvme-mpath: replace direct_make_request with generic_make_request" has been added to the 5.4-stable tree gregkh
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=20210407052806.GA18573@lst.de \
--to=hch@lst.de \
--cc=gregkh@linuxfoundation.org \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=stable@vger.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