On Thu, 2017-11-02 at 08:36 -0400, Shankara Pailoor wrote: > 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
Sorry, we are flooded by such reports, so you have to give the exact details, and find a C repro. A bonus if you actually send a kernel patch, of course. Thanks.
