On Sun, Mar 24, 2019 at 7:51 PM syzbot <syzbot+9d8b6fa6ee7636f350c1@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > > syzbot has bisected this bug to: > > commit 86f690e8bfd124c38940e7ad58875ef383003348 > Author: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> > Date: Thu Mar 29 12:15:13 2018 +0000 > > Merge tag 'stm-intel_th-for-greg-20180329' of > git://git.kernel.org/pub/scm/linux/kernel/git/ash/stm into char-misc-next > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17d653a3200000 > start commit: 74c4a24d Add linux-next specific files for 20181207 > git tree: linux-next > final crash: https://syzkaller.appspot.com/x/report.txt?x=143653a3200000 > console output: https://syzkaller.appspot.com/x/log.txt?x=103653a3200000 > kernel config: https://syzkaller.appspot.com/x/.config?x=6e9413388bf37bed > dashboard link: https://syzkaller.appspot.com/bug?extid=9d8b6fa6ee7636f350c1 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16e19da3400000 > > Reported-by: syzbot+9d8b6fa6ee7636f350c1@xxxxxxxxxxxxxxxxxxxxxxxxx > Fixes: 86f690e8bfd1 ("Merge tag 'stm-intel_th-for-greg-20180329' of > git://git.kernel.org/pub/scm/linux/kernel/git/ash/stm into char-misc-next") > > For information about bisection process see: https://goo.gl/tpsmEJ#bisection Looking at the crash patterns in the bisection log it seems that this is a stack overflow/corruption in wb_workfn. There are other reports that suggest that simply causing OOM randomly corrupts kernel memory. The semget is only an easy way to cause OOMs. But since we now sandbox tests processes with sem sysctl and friends, I think we can close this report. #syz invalid Though the kernel memory corruption on OOMs is still there.
