All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+7df4afa14aeda476a7a1@syzkaller.appspotmail.com>
To: 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,  tglx@kernel.org
Subject: Re: [syzbot] [ocfs2?] possible deadlock in ocfs2_xattr_remove
Date: Mon, 17 Aug 2026 16:20:02 -0700	[thread overview]
Message-ID: <6a839722.f7a79266.2f965f.002e.GAE@google.com> (raw)
In-Reply-To: <69725516.a00a0220.3ad28e.ea7a.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=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

  parent reply	other threads:[~2026-08-17 23:20 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 [this message]
2026-08-18  9:16   ` Thomas Gleixner

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=6a839722.f7a79266.2f965f.002e.GAE@google.com \
    --to=syzbot+7df4afa14aeda476a7a1@syzkaller.appspotmail.com \
    --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@kernel.org \
    --cc=syzbot@lists.linux.dev \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=syzkaller-upstream-moderation@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 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.