From: syzbot <syzbot+2e6495950edcf7fbfccf@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, 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_page_mkwrite
Date: Wed, 22 Oct 2025 19:48:03 -0700 [thread overview]
Message-ID: <68f99763.050a0220.346f24.006e.GAE@google.com> (raw)
In-Reply-To: <00000000000093a1ca0621e8d336@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=1357e3e2580000
start commit: b5a24181e461 Merge tag 'trace-ringbuffer-v6.12-rc7-2' of g..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=1503500c6f615d24
dashboard link: https://syzkaller.appspot.com/bug?extid=2e6495950edcf7fbfccf
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17f252e8580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12ecd2c0580000
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
prev parent reply other threads:[~2025-10-23 2:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 9:35 [syzbot] [ocfs2?] possible deadlock in ocfs2_page_mkwrite syzbot
2024-11-17 1:25 ` syzbot
2024-11-17 17:49 ` syzbot
2025-10-23 2:48 ` 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=68f99763.050a0220.346f24.006e.GAE@google.com \
--to=syzbot+2e6495950edcf7fbfccf@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=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