mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+2471d99ca242f0f7a2a3@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,  rgoldwyn@suse.com,
	sandeen@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] possible deadlock in ocfs2_xattr_ibody_find
Date: Tue, 25 Feb 2025 22:38:07 -0800	[thread overview]
Message-ID: <67beb6cf.050a0220.38b081.0003.GAE@google.com> (raw)
In-Reply-To: <674c6006.050a0220.ad585.0036.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit 9be53fe697eccf45e5c37e10ffd399eeca5eb489
Author: Eric Sandeen <sandeen@redhat.com>
Date:   Mon Oct 28 14:41:15 2024 +0000

    ocfs2: convert to the new mount API

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=15fdffdf980000
start commit:   9b2ffa6148b1 Merge tag 'mtd/fixes-for-6.13-rc5' of git://g..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=4c4096b0d467a682
dashboard link: https://syzkaller.appspot.com/bug?extid=2471d99ca242f0f7a2a3
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=172412f8580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=12155adf980000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: ocfs2: convert to the new mount API

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      reply	other threads:[~2025-02-26  6:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-01 13:09 syzbot
2025-02-26  6:38 ` 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=67beb6cf.050a0220.38b081.0003.GAE@google.com \
    --to=syzbot+2471d99ca242f0f7a2a3@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=rgoldwyn@suse.com \
    --cc=sandeen@redhat.com \
    --cc=syzkaller-bugs@googlegroups.com \
    /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®