From: syzbot <syzbot+d7935821694d430624ea@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, jlbec@evilplan.org,
joseph.qi@linux.alibaba.com, linux-kernel@vger.kernel.org,
mark@fasheh.com, ocfs2-devel@lists.linux.dev,
ocfs2-devel@oss.oracle.com, syzkaller-bugs@googlegroups.com,
torvalds@linux-foundation.org, vvidic@valentin-vidic.from.hr
Subject: Re: [syzbot] [ocfs2?] INFO: trying to register non-static key in ocfs2_dlm_shutdown
Date: Fri, 08 Nov 2024 14:52:06 -0800 [thread overview]
Message-ID: <672e9616.050a0220.138bd5.0034.GAE@google.com> (raw)
In-Reply-To: <66e9830e.050a0220.115905.000e.GAE@google.com>
syzbot has bisected this issue to:
commit da5e7c87827e8caa6a1eeec6d95dcf74ab592a01
Author: Valentin Vidic <vvidic@valentin-vidic.from.hr>
Date: Fri Nov 5 20:34:49 2021 +0000
ocfs2: cleanup journal init and shutdown
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=128b2ea7980000
start commit: c88416ba074a Add linux-next specific files for 20241101
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=118b2ea7980000
console output: https://syzkaller.appspot.com/x/log.txt?x=168b2ea7980000
kernel config: https://syzkaller.appspot.com/x/.config?x=704b6be2ac2f205f
dashboard link: https://syzkaller.appspot.com/bug?extid=d7935821694d430624ea
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1445ab40580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1200e987980000
Reported-by: syzbot+d7935821694d430624ea@syzkaller.appspotmail.com
Fixes: da5e7c87827e ("ocfs2: cleanup journal init and shutdown")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-11-08 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 13:24 [syzbot] [ocfs2?] INFO: trying to register non-static key in ocfs2_dlm_shutdown syzbot
2024-10-19 6:17 ` syzbot
2024-11-08 22:52 ` syzbot [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=672e9616.050a0220.138bd5.0034.GAE@google.com \
--to=syzbot+d7935821694d430624ea@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=ocfs2-devel@oss.oracle.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=vvidic@valentin-vidic.from.hr \
/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