From: Thomas Gleixner <tglx@kernel.org>
To: syzbot <syzbot+7df4afa14aeda476a7a1@syzkaller.appspotmail.com>,
jlbec@evilplan.org, joseph.qi@linux.alibaba.com,
linux-kernel@vger.kernel.org, mark@fasheh.com, nogikh@google.com,
ocfs2-devel@lists.linux.dev, syzbot@kernel.org,
syzbot@lists.linux.dev, syzkaller-bugs@googlegroups.com,
syzkaller-upstream-moderation@googlegroups.com,
teddy.astie@vates.tech
Subject: Re: [syzbot] [ocfs2?] possible deadlock in ocfs2_xattr_remove
Date: Tue, 18 Aug 2026 11:16:10 +0200 [thread overview]
Message-ID: <875x17lrfp.ffs@fw13> (raw)
In-Reply-To: <6a839722.f7a79266.2f965f.002e.GAE@google.com>
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
prev parent reply other threads:[~2026-08-18 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 16:49 [syzbot] [ocfs2?] possible deadlock in ocfs2_xattr_remove syzbot
2026-05-07 10:52 ` syzbot
2026-08-17 23:20 ` syzbot
2026-08-18 9:16 ` Thomas Gleixner [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=875x17lrfp.ffs@fw13 \
--to=tglx@kernel.org \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=nogikh@google.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=syzbot+7df4afa14aeda476a7a1@syzkaller.appspotmail.com \
--cc=syzbot@kernel.org \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=syzkaller-upstream-moderation@googlegroups.com \
--cc=teddy.astie@vates.tech \
/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.