mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+ca440b457d21568f8021@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, elic@nvidia.com, jasowang@redhat.com,
	 jlbec@evilplan.org, joseph.qi@linux.alibaba.com,
	linux-kernel@vger.kernel.org,  lizhi.xu@windriver.com,
	mark.tinguely@oracle.com, mark@fasheh.com,  mst@redhat.com,
	ocfs2-devel@lists.linux.dev, ocfs2-devel@oss.oracle.com,
	 parav@nvidia.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] possible deadlock in ocfs2_fiemap
Date: Thu, 23 Oct 2025 01:33:03 -0700	[thread overview]
Message-ID: <68f9e83f.a70a0220.3bf6c6.0035.GAE@google.com> (raw)
In-Reply-To: <000000000000cb688206213d1bda@google.com>

syzbot suspects this issue was fixed by commit:

commit 04100f775c2ea501927f508f17ad824ad1f23c8d
Author: Mark Tinguely <mark.tinguely@oracle.com>
Date:   Fri Aug 29 15:18:15 2025 +0000

    ocfs2: fix recursive semaphore deadlock in fiemap call

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13bead42580000
start commit:   c330cb607721 Merge tag 'i2c-for-6.17-rc3' of git://git.ker..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=e1e1566c7726877e
dashboard link: https://syzkaller.appspot.com/bug?extid=ca440b457d21568f8021
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=133b6c42580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10b9a862580000

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

#syz fix: ocfs2: fix recursive semaphore deadlock in fiemap call

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

  parent reply	other threads:[~2025-10-23  8:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03 20:43 syzbot
2024-09-29  7:52 ` syzbot
2024-10-17  8:55   ` [PATCH] ocfs2: Fix " Lizhi Xu
2024-10-11 20:59 ` [syzbot] [ocfs2?] " syzbot
2024-10-17  1:52 ` [syzbot] " syzbot
2024-10-17  3:19 ` syzbot
2025-10-23  8:33 ` syzbot [this message]
     [not found] <20241017015210.3665821-1-lizhi.xu@windriver.com>
2024-10-17  2:18 ` syzbot
     [not found] <20241017031934.156050-1-lizhi.xu@windriver.com>
2024-10-17  3:51 ` syzbot

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=68f9e83f.a70a0220.3bf6c6.0035.GAE@google.com \
    --to=syzbot+ca440b457d21568f8021@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=elic@nvidia.com \
    --cc=jasowang@redhat.com \
    --cc=jlbec@evilplan.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizhi.xu@windriver.com \
    --cc=mark.tinguely@oracle.com \
    --cc=mark@fasheh.com \
    --cc=mst@redhat.com \
    --cc=ocfs2-devel@lists.linux.dev \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=parav@nvidia.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®