[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <68f99763.050a0220.346f24.006e.GAE@google.com>
Date: Wed, 22 Oct 2025 19:48:03 -0700
From: syzbot <syzbot+2e6495950edcf7fbfccf@...kaller.appspotmail.com>
To: akpm@...ux-foundation.org, elic@...dia.com, jasowang@...hat.com,
jlbec@...lplan.org, joseph.qi@...ux.alibaba.com, linux-kernel@...r.kernel.org,
mark.tinguely@...cle.com, mark@...heh.com, mst@...hat.com,
ocfs2-devel@...ts.linux.dev, ocfs2-devel@....oracle.com, parav@...dia.com,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [ocfs2?] possible deadlock in ocfs2_page_mkwrite
syzbot suspects this issue was fixed by commit:
commit 04100f775c2ea501927f508f17ad824ad1f23c8d
Author: Mark Tinguely <mark.tinguely@...cle.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
Powered by blists - more mailing lists