From: syzbot <syzbot+31eb4d4e7d9bc1fc1312@syzkaller.appspotmail.com>
To: 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, inwardvessel@gmail.com,
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, mkoutny@suse.com,
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: Sun, 01 Jun 2025 09:21:02 -0700 [thread overview]
Message-ID: <683c7dee.a00a0220.d8eae.0032.GAE@google.com> (raw)
In-Reply-To: <6751e769.050a0220.b4160.01df.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit a97915559f5c5ff1972d678b94fd460c72a3b5f2
Author: JP Kobryn <inwardvessel@gmail.com>
Date: Fri Apr 4 01:10:48 2025 +0000
cgroup: change rstat function signatures from cgroup-based to css-based
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12ca4c82580000
start commit: 932fc2f19b74 Merge branch 'irq-save-restore'
git tree: bpf-next
kernel config: https://syzkaller.appspot.com/x/.config?x=50c7a61469ce77e7
dashboard link: https://syzkaller.appspot.com/bug?extid=31eb4d4e7d9bc1fc1312
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=161cdfc0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12dfc8df980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: cgroup: change rstat function signatures from cgroup-based to css-based
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-06-01 16:21 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 [this message]
2025-06-02 14:15 ` Michal Koutný
2025-06-17 10:00 ` Michal Koutný
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=683c7dee.a00a0220.d8eae.0032.GAE@google.com \
--to=syzbot+31eb4d4e7d9bc1fc1312@syzkaller.appspotmail.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=mkoutny@suse.com \
--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=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 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.