From: Valentin Kleibel <valentin@vrvis.at>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Justin Sanders <justin@coraid.com>,
linux-block@vger.kernel.org
Subject: Re: [PATCH] block: aoe: fix page fault in freedev()
Date: Thu, 10 Mar 2022 13:24:38 +0100 [thread overview]
Message-ID: <50ddedf1-5ac3-91c3-0b50-645ceb541071@vrvis.at> (raw)
In-Reply-To: <YinpIKY0HVlJ+TLR@kroah.com>
On 10/03/2022 13:03, Greg Kroah-Hartman wrote:
>> This patch applies to kernels 5.4 and 5.10.
>
> We need a fix for Linus's tree first before we can backport anything to
> older kernels. Does this also work there?
It is fixed in Linus' tree starting with 5.14.
The patch reproduces the behavior of the current master introduced in
commit 6560ec961a08 (aoe: use blk_mq_alloc_disk and blk_cleanup_disk).
>> Fixes: 3582dd2 (aoe: convert aoeblk to blk-mq)
>
> A few more digits in the sha1 here would be good, otherwise our tools
> will complain. It should look like:
> Fixes: 3582dd291788 ("aoe: convert aoeblk to blk-mq")
thanks for the hint, i will do so in the future.
cheers,
valentin
next prev parent reply other threads:[~2022-03-10 12:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 11:53 [PATCH] block: aoe: fix page fault in freedev() Valentin Kleibel
2022-03-10 12:03 ` Greg Kroah-Hartman
2022-03-10 12:24 ` Valentin Kleibel [this message]
2022-03-10 12:26 ` Greg Kroah-Hartman
2022-03-10 12:55 ` Valentin Kleibel
2022-03-14 11:12 ` Greg Kroah-Hartman
2022-03-31 9:58 ` [PATCH v2 0/2] " Valentin Kleibel
2022-03-31 10:00 ` [PATCH v2 1/2] block: add blk_alloc_disk and blk_cleanup_disk APIs Valentin Kleibel
2022-04-11 14:43 ` Greg Kroah-Hartman
2022-03-31 10:01 ` [PATCH v2 2/2] aoe: use blk_mq_alloc_disk and blk_cleanup_disk Valentin Kleibel
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=50ddedf1-5ac3-91c3-0b50-645ceb541071@vrvis.at \
--to=valentin@vrvis.at \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=justin@coraid.com \
--cc=linux-block@vger.kernel.org \
--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