From: Greg KH <gregkh@linuxfoundation.org>
To: Jan Kara <jack@suse.cz>
Cc: axboe@kernel.dk, hch@lst.de, yukuai3@huawei.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] bfq: Split shared queues on move between cgroups" failed to apply to 4.19-stable tree
Date: Mon, 6 Jun 2022 16:48:18 +0200 [thread overview]
Message-ID: <Yp4TsgtHMR/nTjF5@kroah.com> (raw)
In-Reply-To: <20220606130253.h2khtboi3nka7d3c@quack3.lan>
On Mon, Jun 06, 2022 at 03:02:53PM +0200, Jan Kara wrote:
> Hello Greg!
>
> I've seen this patch failed to apply to 4.19 and 4.14 stable trees but
> you've still merged (some) of the patches following this one from the same
> series. Honestly, I would not consider the result very trustworthy. The
> code involved is rather complex with subtle interactions across subsystems.
> So please remove also upstream commits:
>
> ea591cd4eb27 ("bfq: Update cgroup information before merging bio")
> fc84e1f941b9 ("bfq: Drop pointless unlock-lock pair")
> 5f550ede5edf ("bfq: Remove pointless bfq_init_rq() calls")
> 09f871868080 ("bfq: Track whether bfq_group is still online")
> 4e54a2493e58 ("bfq: Get rid of __bio_blkcg() usage")
> 075a53b78b81 ("bfq: Make sure bfqg for which we are queueing requests is online")
>
> from 4.14 and 4.19 stable queues. If someone will need these fixes there,
> he'll need to do proper backport with targetted testing etc... Thanks!
Only 2 ended up applying there, so I've dropped those two now, thanks!
greg k-h
prev parent reply other threads:[~2022-06-06 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 11:57 FAILED: patch "[PATCH] bfq: Split shared queues on move between cgroups" failed to apply to 4.19-stable tree gregkh
2022-06-06 13:02 ` Jan Kara
2022-06-06 14:48 ` Greg KH [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=Yp4TsgtHMR/nTjF5@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=stable@vger.kernel.org \
--cc=yukuai3@huawei.com \
/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