Hi, On Wed, Mar 05 2025 at 16:15:20, Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx> wrote: > Greg, could you please hold on to this for a while? > I was not able to reproduce this and am waiting for Ricardo's config. > I would like to understand how this is possible since I don't see the > problem based on audit. Sorry I missed the email where you requested the kernel config, here it is: https://pastebin.com/0Y5aEx71 Added context and remarks: even with this kernel config and the C reproducer I shared earlier, there's no guarantee that you'll be able to reproduce the issue, as it may depend on some specifics of the particular runtime environment it was triggered on. I couldn't reproduce it on qemu but the syzkaller instance that raised the issue could reproduce it deterministically on the target setup and that's what I used to test the patch. I shared the reproducer as an example and as additional information, for illustrative purposes, I'm sorry I wasn't clear on that. Regards, Ricardo
