From: syzbot <syzbot+c6c4861455fdd207f160@syzkaller.appspotmail.com>
To: andrii@kernel.org, asml.silence@gmail.com, ast@kernel.org,
axboe@kernel.dk, bpf@vger.kernel.org, daniel@iogearbox.net,
eddyz87@gmail.com, haoluo@google.com, john.fastabend@gmail.com,
jolsa@kernel.org, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, martin.lau@linux.dev,
mingo@kernel.org, netdev@vger.kernel.org, peterz@infradead.org,
riel@redhat.com, sdf@fomichev.me, sdf@google.com,
song@kernel.org, syzkaller-bugs@googlegroups.com,
wander@redhat.com, yhs@fb.com, yonghong.song@linux.dev
Subject: Re: [syzbot] [bpf?] BUG: MAX_STACK_TRACE_ENTRIES too low! (4)
Date: Sun, 29 Sep 2024 00:25:02 -0700 [thread overview]
Message-ID: <66f900ce.050a0220.aab67.000f.GAE@google.com> (raw)
In-Reply-To: <66f62bf3.050a0220.38ace9.0007.GAE@google.com>
syzbot has bisected this issue to:
commit 893cdaaa3977be6afb3a7f756fbfd7be83f68d8c
Author: Wander Lairson Costa <wander@redhat.com>
Date: Wed Jun 14 12:23:22 2023 +0000
sched: avoid false lockdep splat in put_task_struct()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14a00127980000
start commit: abf2050f51fd Merge tag 'media/v6.12-1' of git://git.kernel..
git tree: bpf
final oops: https://syzkaller.appspot.com/x/report.txt?x=16a00127980000
console output: https://syzkaller.appspot.com/x/log.txt?x=12a00127980000
kernel config: https://syzkaller.appspot.com/x/.config?x=bc30a30374b0753
dashboard link: https://syzkaller.appspot.com/bug?extid=c6c4861455fdd207f160
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14ee7107980000
Reported-by: syzbot+c6c4861455fdd207f160@syzkaller.appspotmail.com
Fixes: 893cdaaa3977 ("sched: avoid false lockdep splat in put_task_struct()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-09-29 7:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 3:52 [syzbot] [bpf?] BUG: MAX_STACK_TRACE_ENTRIES too low! (4) syzbot
2024-09-29 7:25 ` syzbot [this message]
2024-11-27 7:07 ` syzbot
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=66f900ce.050a0220.aab67.000f.GAE@google.com \
--to=syzbot+c6c4861455fdd207f160@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=asml.silence@gmail.com \
--cc=ast@kernel.org \
--cc=axboe@kernel.dk \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=sdf@fomichev.me \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wander@redhat.com \
--cc=yhs@fb.com \
--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