* Re: [syzbot] [ocfs2?] possible deadlock in ocfs2_xattr_remove [not found] <69725516.a00a0220.3ad28e.ea7a.GAE@google.com> @ 2026-08-17 23:20 ` syzbot 2026-08-18 9:16 ` Thomas Gleixner 0 siblings, 1 reply; 2+ messages in thread From: syzbot @ 2026-08-17 23:20 UTC (permalink / raw) To: jlbec, joseph.qi, linux-kernel, mark, nogikh, ocfs2-devel, syzbot, syzbot, syzkaller-bugs, syzkaller-upstream-moderation, teddy.astie, tglx 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=156f3949580000 start commit: 5862221fdded Merge tag 'parisc-for-7.1-rc3' of git://git.k.. git tree: upstream kernel config: https://syzkaller.appspot.com/x/.config?x=f2e8ebfec4636d32 dashboard link: https://syzkaller.appspot.com/bug?extid=7df4afa14aeda476a7a1 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10f2200e580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11ae9636580000 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 ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [syzbot] [ocfs2?] possible deadlock in ocfs2_xattr_remove 2026-08-17 23:20 ` [syzbot] [ocfs2?] possible deadlock in ocfs2_xattr_remove syzbot @ 2026-08-18 9:16 ` Thomas Gleixner 0 siblings, 0 replies; 2+ messages in thread From: Thomas Gleixner @ 2026-08-18 9:16 UTC (permalink / raw) To: syzbot, jlbec, joseph.qi, linux-kernel, mark, nogikh, ocfs2-devel, syzbot, syzbot, syzkaller-bugs, syzkaller-upstream-moderation, teddy.astie On Mon, Aug 17 2026 at 16:20, syzbot wrote: > 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 That is completely unrelated and fixes an early boot issue which manifest way before you can start your test case. The lockdep splat is purely about OCFS2 internal locking. Your bisection took a wrong turn somewhere. Thanks, tglx ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-08-18 9:16 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <69725516.a00a0220.3ad28e.ea7a.GAE@google.com>
2026-08-17 23:20 ` [syzbot] [ocfs2?] possible deadlock in ocfs2_xattr_remove syzbot
2026-08-18 9:16 ` Thomas Gleixner
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox