From: syzbot <syzbot+6ea37e2e6ffccf41a7e6@syzkaller.appspotmail.com>
To: bigeasy@linutronix.de, boqun.feng@gmail.com,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
longman@redhat.com, syzkaller-bugs@googlegroups.com,
tj@kernel.org
Subject: Re: [syzbot] [kernfs?] WARNING: locking bug in kernfs_path_from_node
Date: Mon, 04 Nov 2024 23:58:03 -0800 [thread overview]
Message-ID: <6729d00b.050a0220.2edce.1505.GAE@google.com> (raw)
In-Reply-To: <67251dc6.050a0220.529b6.015e.GAE@google.com>
syzbot has bisected this issue to:
commit 560af5dc839eef08a273908f390cfefefb82aa04
Author: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Date: Wed Oct 9 15:45:03 2024 +0000
lockdep: Enable PROVE_RAW_LOCK_NESTING with PROVE_LOCKING.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12d13587980000
start commit: f9f24ca362a4 Add linux-next specific files for 20241031
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=11d13587980000
console output: https://syzkaller.appspot.com/x/log.txt?x=16d13587980000
kernel config: https://syzkaller.appspot.com/x/.config?x=328572ed4d152be9
dashboard link: https://syzkaller.appspot.com/bug?extid=6ea37e2e6ffccf41a7e6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13119340580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14d56630580000
Reported-by: syzbot+6ea37e2e6ffccf41a7e6@syzkaller.appspotmail.com
Fixes: 560af5dc839e ("lockdep: Enable PROVE_RAW_LOCK_NESTING with PROVE_LOCKING.")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-11-05 7:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 18:28 [syzbot] [kernfs?] WARNING: locking bug in kernfs_path_from_node syzbot
2024-11-05 7:58 ` syzbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-08 23:16 [PATCH] kernfs: Use RCU for kernfs_node::name lookup Hillf Danton
2024-11-08 23:48 ` [syzbot] [kernfs?] WARNING: locking bug in kernfs_path_from_node 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=6729d00b.050a0220.2edce.1505.GAE@google.com \
--to=syzbot+6ea37e2e6ffccf41a7e6@syzkaller.appspotmail.com \
--cc=bigeasy@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
/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.