From: "Michal Koutný" <mkoutny@suse.com>
To: syzbot <syzbot+31eb4d4e7d9bc1fc1312@syzkaller.appspotmail.com>,
inwardvessel@gmail.com
Cc: akpm@linux-foundation.org, andrii@kernel.org, ast@kernel.org,
axboe@kernel.dk, bpf@vger.kernel.org, cgroups@vger.kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, hannes@cmpxchg.org,
haoluo@google.com, hawk@kernel.org, john.fastabend@gmail.com,
jolsa@kernel.org, josef@toxicpanda.com, kpsingh@kernel.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-mm@kvack.org,
martin.lau@linux.dev, mhocko@kernel.org, muchun.song@linux.dev,
mykolal@fb.com, netdev@vger.kernel.org, roman.gushchin@linux.dev,
sdf@fomichev.me, shakeel.butt@linux.dev, shuah@kernel.org,
song@kernel.org, syzkaller-bugs@googlegroups.com, tj@kernel.org,
yonghong.song@linux.dev
Subject: Re: [syzbot] [cgroups?] general protection fault in __cgroup_rstat_lock
Date: Tue, 17 Jun 2025 12:00:51 +0200 [thread overview]
Message-ID: <qzzfped7jds7kcr466zahbrcw2eg5n6ke7drzxm6btexv36ca2@mici3xiuajuz> (raw)
In-Reply-To: <p32ytuin2hmxacacroykhtfxf6l5l7sji33dt4xknnojqm4xh2@hrldb5d6fgfj>
[-- Attachment #1: Type: text/plain, Size: 680 bytes --]
On Mon, Jun 02, 2025 at 04:15:56PM +0200, Michal Koutný <mkoutny@suse.com> wrote:
> I'd say this might be relevant (although I don't see the possibly
> incorrect error handlnig path) but it doesn't mean this commit fixes it,
> it'd rather require the reproducer to adjust the N on this path.
Hm, possibly syzbot caught up here [1]:
-mkdir(&(0x7f0000000000)='./cgroup/file0\x00', 0xd0939199c36b4d28) (fail_nth: 8)
+mkdirat$cgroup_root(0xffffffffffffff9c, &(0x7f00000005c0)='./cgroup.net/syz0\x00', 0x1ff) (fail_nth: 23)
So there's something fishy in the error handling.
HTH,
Michal
[1] https://lore.kernel.org/lkml/68403875.a00a0220.d4325.000a.GAE@google.com/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-06-17 10:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 17:48 [syzbot] [cgroups?] general protection fault in __cgroup_rstat_lock syzbot
2024-12-11 19:52 ` Tejun Heo
2024-12-11 20:21 ` syzbot
2024-12-11 20:48 ` Tejun Heo
2025-06-01 16:21 ` syzbot
2025-06-02 14:15 ` Michal Koutný
2025-06-17 10:00 ` Michal Koutný [this message]
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=qzzfped7jds7kcr466zahbrcw2eg5n6ke7drzxm6btexv36ca2@mici3xiuajuz \
--to=mkoutny@suse.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=axboe@kernel.dk \
--cc=bpf@vger.kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=haoluo@google.com \
--cc=hawk@kernel.org \
--cc=inwardvessel@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=josef@toxicpanda.com \
--cc=kpsingh@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=martin.lau@linux.dev \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=mykolal@fb.com \
--cc=netdev@vger.kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=sdf@fomichev.me \
--cc=shakeel.butt@linux.dev \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=syzbot+31eb4d4e7d9bc1fc1312@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
--cc=yonghong.song@linux.dev \
/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).