cgroups.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: JP Kobryn <inwardvessel@gmail.com>
To: syzbot <syzbot+8d052e8b99e40bc625ed@syzkaller.appspotmail.com>,
	cgroups@vger.kernel.org, hannes@cmpxchg.org,
	linux-kernel@vger.kernel.org, mkoutny@suse.com,
	syzkaller-bugs@googlegroups.com, tj@kernel.org,
	Shakeel Butt <shakeel.butt@linux.dev>
Subject: Re: [syzbot] [cgroups?] WARNING in css_rstat_exit
Date: Mon, 14 Jul 2025 16:58:29 -0700	[thread overview]
Message-ID: <65df1f7e-9512-4527-bbe4-0cf10877f4ba@gmail.com> (raw)
In-Reply-To: <6874b1d8.a70a0220.3b380f.0051.GAE@google.com>

On 7/14/25 12:29 AM, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
> 
> HEAD commit:    5d5d62298b8b Merge tag 'x86_urgent_for_v6.16_rc6' of git:/..
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=11dabd82580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=84eae426cbd8669c
> dashboard link: https://syzkaller.appspot.com/bug?extid=8d052e8b99e40bc625ed
> compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=162c47d4580000

#syz test

diff --git a/kernel/cgroup/cgroup.c b/kernel/cgroup/cgroup.c
index a723b7dc6e4e..e6c5c998ead6 100644
--- a/kernel/cgroup/cgroup.c
+++ b/kernel/cgroup/cgroup.c
@@ -5669,6 +5669,12 @@ static struct cgroup_subsys_state 
*css_create(struct cgroup *cgrp,

  	init_and_link_css(css, ss, cgrp);

+	err = css_rstat_init(css);
+	if (err) {
+		ss->css_free(css);
+		goto err_out;
+	}
+
  	err = percpu_ref_init(&css->refcnt, css_release, 0, GFP_KERNEL);
  	if (err)
  		goto err_free_css;
@@ -5678,10 +5684,6 @@ static struct cgroup_subsys_state 
*css_create(struct cgroup *cgrp,
  		goto err_free_css;
  	css->id = err;

-	err = css_rstat_init(css);
-	if (err)
-		goto err_free_css;
-
  	/* @css is ready to be brought online now, make it visible */
  	list_add_tail_rcu(&css->sibling, &parent_css->children);
  	cgroup_idr_replace(&ss->css_idr, css, css->id);
@@ -5697,6 +5699,7 @@ static struct cgroup_subsys_state 
*css_create(struct cgroup *cgrp,
  err_free_css:
  	INIT_RCU_WORK(&css->destroy_rwork, css_free_rwork_fn);
  	queue_rcu_work(cgroup_destroy_wq, &css->destroy_rwork);
+err_out:
  	return ERR_PTR(err);
  }

--

  parent reply	other threads:[~2025-07-14 23:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13 16:55 [syzbot] [cgroups?] WARNING in css_rstat_exit syzbot
2025-06-16  9:49 ` Michal Koutný
2025-06-17  4:46   ` JP Kobryn
2025-07-14  7:29 ` syzbot
2025-07-14 23:37   ` JP Kobryn
2025-07-14 23:39     ` syzbot
2025-07-14 23:58   ` JP Kobryn [this message]
2025-07-15  0:00     ` syzbot
2025-07-15  1:05   ` JP Kobryn
2025-07-15  1:27     ` syzbot
2025-07-17 13:28     ` Michal Koutný
2025-07-17 18:46       ` Shakeel Butt
2025-07-22  0:29         ` JP Kobryn

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=65df1f7e-9512-4527-bbe4-0cf10877f4ba@gmail.com \
    --to=inwardvessel@gmail.com \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkoutny@suse.com \
    --cc=shakeel.butt@linux.dev \
    --cc=syzbot+8d052e8b99e40bc625ed@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tj@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;
as well as URLs for NNTP newsgroup(s).