From: syzbot <syzbot+b506de56cbbb63148c33@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, frederic@kernel.org,
haoluo@google.com, houtao@huaweicloud.com,
john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, martin.lau@linux.dev,
peterz@infradead.org, sdf@fomichev.me, song@kernel.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
yonghong.song@linux.dev
Subject: Re: [syzbot] [bpf?] WARNING: locking bug in trie_delete_elem
Date: Thu, 07 Nov 2024 13:00:02 -0800 [thread overview]
Message-ID: <672d2a52.050a0220.15a23d.01a1.GAE@google.com> (raw)
In-Reply-To: <6723db4a.050a0220.35b515.0168.GAE@google.com>
syzbot has bisected this issue to:
commit 4febce44cfebcb490b196d5d10ae9f403ca4c956
Author: Thomas Gleixner <tglx@linutronix.de>
Date: Tue Oct 1 08:42:03 2024 +0000
posix-timers: Cure si_sys_private race
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=129f2d87980000
start commit: f9f24ca362a4 Add linux-next specific files for 20241031
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=169f2d87980000
kernel config: https://syzkaller.appspot.com/x/.config?x=328572ed4d152be9
dashboard link: https://syzkaller.appspot.com/bug?extid=b506de56cbbb63148c33
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1387655f980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11ac5540580000
Reported-by: syzbot+b506de56cbbb63148c33@syzkaller.appspotmail.com
Fixes: 4febce44cfeb ("posix-timers: Cure si_sys_private race")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-11-07 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 19:32 [syzbot] [bpf?] WARNING: locking bug in trie_delete_elem syzbot
2024-11-01 9:44 ` [RESEND] " Hou Tao
2024-11-07 21:00 ` syzbot [this message]
2024-11-12 2:24 ` Thomas Gleixner
2024-11-13 11:04 ` Aleksandr Nogikh
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=672d2a52.050a0220.15a23d.01a1.GAE@google.com \
--to=syzbot+b506de56cbbb63148c33@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=frederic@kernel.org \
--cc=haoluo@google.com \
--cc=houtao@huaweicloud.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=peterz@infradead.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--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.