Hi, We encountered the following warning when fuzzing with Syzkaller on Linux 4.14-rc4. Syzkaller was able to isolate the sequence of calls which caused the bug but couldn't create a C program that could regularly trigger it.
Here are the logs from the reproducer attempts: https://pastebin.com/QWQZK6hW Here is the original stack trace: https://pastebin.com/7L4WciRr Regards, Shankara
