From: Tejun Heo <tj@kernel.org>
To: Edward Adam Davis <eadavis@qq.com>
Cc: cgroups@vger.kernel.org, chenridong@huaweicloud.com,
hannes@cmpxchg.org, linux-kernel@vger.kernel.org,
mkoutny@suse.com,
syzbot+33e571025d88efd1312c@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH v2] sched/psi: fix race between file release and pressure write
Date: Fri, 10 Apr 2026 09:14:05 -1000 [thread overview]
Message-ID: <adlL_QXVAgCBH9L8@slm.duckdns.org> (raw)
In-Reply-To: <tencent_6F3C1F36BA97BA37AA4A2C7403766F675A09@qq.com>
Hello,
On Fri, Apr 10, 2026 at 08:39:45PM +0800, Edward Adam Davis wrote:
> static ssize_t pressure_write(struct kernfs_open_file *of, char *buf,
> size_t nbytes, enum psi_res res)
> {
> - struct cgroup_file_ctx *ctx = of->priv;
> + struct cgroup_file_ctx *ctx;
> struct psi_trigger *new;
> struct cgroup *cgrp;
> struct psi_group *psi;
> + ssize_t ret = 0;
>
> cgrp = cgroup_kn_lock_live(of->kn, false);
> if (!cgrp)
> return -ENODEV;
>
> + ctx = of->priv;
> + if (!ctx) {
This test likely isn't necessary but that's pre-existing.
> + ret = -ENODEV;
> + goto out_unlock;
> + }
> +
> cgroup_get(cgrp);
We don't need get/put if we don't drop the mutex, right?
Thanks.
--
tejun
next prev parent reply other threads:[~2026-04-10 19:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 10:04 [syzbot] [cgroups?] KASAN: slab-use-after-free Read in pressure_write syzbot
2026-04-10 4:00 ` [PATCH] sched/psi: fix race between file release and pressure write Edward Adam Davis
2026-04-10 9:00 ` Chen Ridong
2026-04-10 9:45 ` Edward Adam Davis
2026-04-10 12:39 ` [PATCH v2] " Edward Adam Davis
2026-04-10 19:14 ` Tejun Heo [this message]
2026-04-11 4:25 ` Edward Adam Davis
2026-04-11 7:39 ` Tejun Heo
2026-04-11 8:29 ` Edward Adam Davis
2026-04-11 20:40 ` Tejun Heo
2026-04-12 2:32 ` Edward Adam Davis
2026-04-12 2:47 ` [PATCH v3] " Edward Adam Davis
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=adlL_QXVAgCBH9L8@slm.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huaweicloud.com \
--cc=eadavis@qq.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkoutny@suse.com \
--cc=syzbot+33e571025d88efd1312c@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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