From: Greg KH <gregkh@linuxfoundation.org>
To: Tomas Krcka <tomas.krcka@gmail.com>
Cc: stable@vger.kernel.org, Shakeel Butt <shakeel.butt@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
Roman Gushchin <roman.gushchin@linux.dev>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Tomas Krcka <krckatom@amazon.de>
Subject: Re: [PATCH 5.10.y] memcg: protect concurrent access to mem_cgroup_idr
Date: Sun, 8 Sep 2024 15:02:10 +0200 [thread overview]
Message-ID: <2024090810-jailer-overeater-9253@gregkh> (raw)
In-Reply-To: <20240906154140.70821-1-krckatom@amazon.de>
On Fri, Sep 06, 2024 at 03:41:40PM +0000, Tomas Krcka wrote:
> From: Shakeel Butt <shakeel.butt@linux.dev>
>
> commit 9972605a238339b85bd16b084eed5f18414d22db upstream.
To quote the documentation:
When using option 2 or 3 you can ask for your change to be included in specific
stable series. When doing so, ensure the fix or an equivalent is applicable,
submitted, or already present in all newer stable trees still supported. This is
meant to prevent regressions that users might later encounter on updating, if
e.g. a fix merged for 5.19-rc1 would be backported to 5.10.y, but not to 5.15.y.
I've dropped this from the review queue and will wait for all of the
needed versions to be submitted.
thanks,
greg k-h
next prev parent reply other threads:[~2024-09-08 13:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 11:43 FAILED: patch "[PATCH] memcg: protect concurrent access to mem_cgroup_idr" failed to apply to 5.10-stable tree gregkh
2024-09-06 15:41 ` [PATCH 5.10.y] memcg: protect concurrent access to mem_cgroup_idr Tomas Krcka
2024-09-08 13:02 ` Greg KH [this message]
2024-09-09 13:43 ` Krcka, Tomas
2024-09-09 14:04 ` Greg KH
2024-09-09 14:10 ` Krcka, Tomas
2024-09-09 14:45 ` Greg KH
2024-09-09 14:55 ` [PATCH 5.10.y v2] " Tomas Krcka
2024-09-10 7:56 ` Greg KH
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=2024090810-jailer-overeater-9253@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=krckatom@amazon.de \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=stable@vger.kernel.org \
--cc=tomas.krcka@gmail.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