From: Michal Hocko <mhocko@suse.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: akpm@linux-foundation.org, guro@fb.com, hannes@cmpxchg.org,
hughd@google.com, shakeelb@google.com,
torvalds@linux-foundation.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] memcg: fix use-after-free in uncharge_batch" failed to apply to 5.4-stable tree
Date: Wed, 28 Feb 2024 13:31:05 +0100 [thread overview]
Message-ID: <Zd8niX5-e2cAth2X@tiehlicka> (raw)
In-Reply-To: <Zd4EnXYVbZilQR_M@tiehlicka>
On Tue 27-02-24 16:49:50, Michal Hocko wrote:
> On Tue 27-02-24 14:32:20, Greg KH wrote:
> > On Tue, Feb 27, 2024 at 02:29:12PM +0100, Michal Hocko wrote:
> > > Why is this applied to 5.4?
> > > $ git describe-ver 1a3e1f40962c
> > > v5.9-rc1~97^2~97
> > >
> > > I do not see 1a3e1f40962c in 5.4 stable tree. What am I missing?
> >
> > It is queued up for this next round of releases in the 5.4.y and 4.19.y
> > trees.
>
> OK, now I remember the partial backport of 1a3e1f40962c
> (http://lkml.kernel.org/r/20240222030237.82486-1-gongruiqi1@huawei.com)
> but I need to have a look whether the follow up patch is really needed.
AFAICS f1796544a0ca ("memcg: fix use-after-free in uncharge_batch") is
only needed if the full 1a3e1f40962c is backported. The one staged for
5.4 shouldn't need a follow up as it only touches the pcp cache. I would
feel safer if other maintainers double check my thinking though.
Thanks
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2024-02-28 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 13:12 FAILED: patch "[PATCH] memcg: fix use-after-free in uncharge_batch" failed to apply to 5.4-stable tree gregkh
2024-02-27 13:29 ` Michal Hocko
2024-02-27 13:32 ` Greg KH
2024-02-27 15:49 ` Michal Hocko
2024-02-28 12:31 ` Michal Hocko [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=Zd8niX5-e2cAth2X@tiehlicka \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=shakeelb@google.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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