All of lore.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: [PATCH 1/2] cgroup: Make operations on the cgroup root_list RCU safe
Date: Mon, 2 Dec 2024 11:30:35 +0100	[thread overview]
Message-ID: <2024120222-legwarmer-attach-896b@gregkh> (raw)
In-Reply-To: <9953011d972d0ec2f38792e985aac55f2e4fda2e.camel@oracle.com>

On Mon, Dec 02, 2024 at 10:26:54AM +0000, Siddh Raman Pant wrote:
> On Mon, Dec 02 2024 at 15:47:00 +0530, Greg Kroah-Hartman wrote:
> > On Mon, Dec 02, 2024 at 03:41:01PM +0530, Siddh Raman Pant wrote:
> > > From: Yafang Shao <laoar.shao@gmail.com>
> > > 
> > > commit d23b5c577715892c87533b13923306acc6243f93 upstream.
> > > 
> > > At present, when we perform operations on the cgroup root_list, we must
> > > hold the cgroup_mutex, which is a relatively heavyweight lock. In reality,
> > > we can make operations on this list RCU-safe, eliminating the need to hold
> > > the cgroup_mutex during traversal. Modifications to the list only occur in
> > > the cgroup root setup and destroy paths, which should be infrequent in a
> > > production environment. In contrast, traversal may occur frequently.
> > > Therefore, making it RCU-safe would be beneficial.
> > > 
> > > Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
> > > Signed-off-by: Tejun Heo <tj@kernel.org>
> > > [fp: adapt to 5.10 mainly because of changes made by e210a89f5b07
> > >  ("cgroup.c: add helper __cset_cgroup_from_root to cleanup duplicated
> > >  codes")]
> > > Signed-off-by: Fedor Pchelkin <pchelkin@ispras.ru>
> > > [Shivani: Modified to apply on v5.4.y]
> > > Signed-off-by: Shivani Agarwal <shivani.agarwal@broadcom.com>
> > > Reviewed-by: Siddh Raman Pant <siddh.raman.pant@oracle.com>
> > 
> > I'm confused.  You do know what signed-off-by means, right?  When
> > sending a patch on, you MUST sign off on it.
> 
> Even if I'm just *forwarding* the patch already posted on the mailing
> list?

Yes.


  reply	other threads:[~2024-12-02 10:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19  6:01 5.10.225 stable kernel cgroup_mutex not held assertion failure Greg Thelen
2024-09-19  8:47 ` Fedor Pchelkin
2024-09-19  8:51   ` [PATCH 5.10/5.15 1/2] cgroup: Make operations on the cgroup root_list RCU safe Fedor Pchelkin
2024-09-19  8:51     ` [PATCH 5.10/5.15 2/2] cgroup: Move rcu_head up near the top of cgroup_root Fedor Pchelkin
2024-09-19  9:26   ` 5.10.225 stable kernel cgroup_mutex not held assertion failure chenridong
2024-09-20  9:28   ` 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
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 [this message]
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
2024-09-23  8:50 ` 5.10.225 stable kernel cgroup_mutex not held assertion failure Sasha Levin
2024-09-29  0:42   ` Greg Thelen

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=2024120222-legwarmer-attach-896b@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.