public inbox for cgroups@vger.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Siddh Raman Pant <siddh.raman.pant@oracle.com>
Cc: "sashal@kernel.org" <sashal@kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
	"shivani.agarwal@broadcom.com" <shivani.agarwal@broadcom.com>
Subject: Re: 5.10.225 stable kernel cgroup_mutex not held assertion failure
Date: Wed, 20 Nov 2024 15:58:36 +0100	[thread overview]
Message-ID: <2024112022-staleness-caregiver-0707@gregkh> (raw)
In-Reply-To: <c10d6cc49868dd3c471c53fc3c4aba61c33edead.camel@oracle.com>

On Wed, Nov 20, 2024 at 02:46:32PM +0000, Siddh Raman Pant wrote:
> On Wed, Nov 06 2024 at 11:54:32 +0530, Siddh Raman Pant wrote:
> > On Wed, Nov 06 2024 at 11:40:39 +0530, gregkh@linuxfoundation.org
> > wrote:
> > > On Wed, Oct 30, 2024 at 07:29:38AM +0000, Siddh Raman Pant wrote:
> > > > Hello maintainers,
> > > > 
> > > > On Fri, 20 Sep 2024 02:28:03 -0700, Shivani Agarwal wrote:
> > > > > Thanks Fedor.
> > > > > 
> > > > > Upstream commit 1be59c97c83c is merged in 5.4 with commit 10aeaa47e4aa and
> > > > > in 4.19 with commit 27d6dbdc6485. The issue is reproducible in 5.4 and 4.19
> > > > > also.
> > > > > 
> > > > > I am sending the backport patch of d23b5c577715 and a7fb0423c201 for 5.4 and
> > > > > 4.19 in the next email.
> > > > 
> > > > Please backport these changes to stable.
> > > > 
> > > > "cgroup/cpuset: Prevent UAF in proc_cpuset_show()" has already been
> > > > backported and bears CVE-2024-43853. As reported, we may already have
> > > > introduced another problem due to the missing backport.
> > > 
> > > What exact commits are needed here?  Please submit backported and tested
> > > commits and we will be glad to queue them up.
> > > 
> > > thanks,
> > > 
> > > greg k-h
> > 
> > Please see the following thread where Shivani posted the patches:
> > 
> > https://lore.kernel.org/all/20240920092803.101047-1-shivani.agarwal@broadcom.com/
> > 
> > Thanks,
> > Siddh
> 
> Ping...

I don't understand what you want here, sorry.

greg k-h

  reply	other threads:[~2024-11-20 14:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240919-5e2d9ccca61f5022e0b574af-pchelkin@ispras.ru>
2024-09-20  9:28 ` 5.10.225 stable kernel cgroup_mutex not held assertion failure Shivani Agarwal
2024-10-30  7:29   ` Siddh Raman Pant
2024-11-06  6:10     ` gregkh
2024-11-06  6:24       ` Siddh Raman Pant
2024-11-20 14:46         ` Siddh Raman Pant
2024-11-20 14:58           ` gregkh [this message]
2024-11-20 17:47             ` Siddh Raman Pant
2024-11-28 10:40               ` Siddh Raman Pant
2024-12-02  9:45               ` gregkh
2024-12-02  9:59                 ` [PATCH 1/2] cgroup: Make operations on the cgroup root_list RCU safe Siddh Raman Pant
2024-12-02  9:59                   ` [PATCH 2/2] cgroup: Move rcu_head up near the top of cgroup_root Siddh Raman Pant
2024-12-02 10:01                   ` [PATCH 1/2] cgroup: Make operations on the cgroup root_list RCU safe Siddh Raman Pant
2024-12-02 10:06                     ` gregkh
2024-12-02 10:11                       ` Siddh Raman Pant
2024-12-02 10:11                         ` [PATCH 2/2] cgroup: Move rcu_head up near the top of cgroup_root Siddh Raman Pant
2024-12-02 10:17                         ` [PATCH 1/2] cgroup: Make operations on the cgroup root_list RCU safe Greg Kroah-Hartman
2024-12-02 10:26                           ` Siddh Raman Pant
2024-12-02 10:30                             ` gregkh
2024-09-20  9:29 ` [PATCH v4.19] " Shivani Agarwal
2024-09-20  9:29 ` [PATCH v4.19] cgroup: Move rcu_head up near the top of cgroup_root Shivani Agarwal
2024-09-20  9:30 ` [PATCH v5.4] cgroup: Make operations on the cgroup root_list RCU safe Shivani Agarwal
2024-09-20  9:33 ` [PATCH v5.4] cgroup: Move rcu_head up near the top of cgroup_root Shivani Agarwal

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=2024112022-staleness-caregiver-0707@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=shivani.agarwal@broadcom.com \
    --cc=siddh.raman.pant@oracle.com \
    --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