From: syzbot <syzbot+ddde294b94666bb51266@syzkaller.appspotmail.com>
To: jlbec@evilplan.org, joel.granados@kernel.org,
joseph.qi@linux.alibaba.com, linux-kernel@vger.kernel.org,
mark@fasheh.com, ocfs2-devel@lists.linux.dev,
syzkaller-bugs@googlegroups.com, teddy.astie@vates.tech,
tglx@kernel.org
Subject: Re: [syzbot] [ocfs2?] possible deadlock in ocfs2_remove_inode (2)
Date: Sun, 16 Aug 2026 15:41:05 -0700 [thread overview]
Message-ID: <6a823c81.f7a79266.2f965f.001b.GAE@google.com> (raw)
In-Reply-To: <678e8256.050a0220.303755.0081.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit f24df84cbe05e4471c04ac4b921fc0340bbc7752
Author: Thomas Gleixner <tglx@kernel.org>
Date: Tue Jun 9 15:14:45 2026 +0000
time/jiffies: Register jiffies clocksource before usage
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=100b7a79580000
start commit: 2d3090a8aeb5 Merge tag 'v7.1-p5' of git://git.kernel.org/p..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=f9e42545d0c4344f
dashboard link: https://syzkaller.appspot.com/bug?extid=ddde294b94666bb51266
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=157bb0ae580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15c4e0ae580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: time/jiffies: Register jiffies clocksource before usage
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2026-08-16 22:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 17:05 syzbot
2026-06-09 21:26 ` syzbot
2026-08-16 22:41 ` 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=6a823c81.f7a79266.2f965f.001b.GAE@google.com \
--to=syzbot+ddde294b94666bb51266@syzkaller.appspotmail.com \
--cc=jlbec@evilplan.org \
--cc=joel.granados@kernel.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=teddy.astie@vates.tech \
--cc=tglx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®