On Mon, 2025-07-28 at 15:40 +0800, Chenzhi Yang wrote: > > Hi Slava, > > Thank you for taking your time. > > > We originally obtained this issue's syz and C reproducers using Syzkaller's repro tool (refer to the URL below). The issue was triggered when we ran the syz reproducer through Syzkaller. > > > Url: https://github.com/google/syzkaller/blob/master/docs/reproducing_crashes.md > > > Syzkaller also provides syz-execprog to verify whether the C program can trigger the issue. We are currently in the process of verifying whether the C reproducer can reliably reproduce the issue. Please allow us some time to complete this verification. > > > We'll follow up with you once we have more concrete results. > > > Best regards, > > Kun > > Hi Kun, > > Just wanted to follow up, how is the verification of the C reproducer going? > If it does reliably reproduce the issue, could you also let us know under what > scenario or environment it occurs? > I already shared the patch [1] for this issue. Thanks, Slava. [1] https://lore.kernel.org/linux-fsdevel/20250703214804.244077-1-slava@xxxxxxxxxxx/
