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 v2 0/2] block: aoe: fix page fault in freedev()
Date: Thu, 31 Mar 2022 11:58:18 +0200 [thread overview]
Message-ID: <b19953f8-2097-6962-eceb-5d41f4639ce4@vrvis.at> (raw)
In-Reply-To: <Yi8jO3Q+xbPx0JwF@kroah.com>
> I do not know, sorry. But we prefer the upstream commits as much as
> possible as one-off changes like this are almost always buggy and wrong
> in the end.
>
> Try doing the backports and see what that looks like please.
I did the backports now but Christoph Hellwig already pointed out:
> No idea what is hidden in bugzilla, but the blk_mq_alloc_disk changes
> aren't easily backportable.
[https://lore.kernel.org/all/20220308060916.GB23629@lst.de/]
Therefore I cherry-picked only the changes for blk_cleanup_disk as they
are much simpler than the changes to blk_mq_alloc_disk.
I kept the original commit messages, please tell me if you feel they
should be changed or do so yourself.
Please apply to 5.4 and 5.10.
Cheers,
Valentin
changelog:
v2:
* cherry pick from upstream commits instead of creating a new patch
next prev parent reply other threads:[~2022-03-31 9:58 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
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 ` Valentin Kleibel [this message]
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=b19953f8-2097-6962-eceb-5d41f4639ce4@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