On Thu, Feb 28, 2019 at 11:11 AM Tetsuo Handa <penguin-ker...@i-love.sakura.ne.jp> wrote: > > On 2019/02/28 15:42, syzbot wrote: > > Hello, > > > > syzbot found the following crash on: > > > > HEAD commit: 7b827ff9af88 Add linux-next specific files for 20190227 > > git tree: linux-next > > console output: https://syzkaller.appspot.com/x/log.txt?x=10f71894c00000 > > kernel config: https://syzkaller.appspot.com/x/.config?x=5fa6b8975759dcc5 > > dashboard link: https://syzkaller.appspot.com/bug?extid=29569ed06425fcf67a95 > > compiler: gcc (GCC) 9.0.0 20181231 (experimental) > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=113a8242c00000 > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=154d6bd0c00000 > > > > IMPORTANT: if you fix the bug, please add the following tag to the commit: > > Reported-by: syzbot+29569ed06425fcf67...@syzkaller.appspotmail.com > > > > Memory allocation failure due to fault injection before loading policy. > > #syz dup: kernel panic: MAC Initialization failed.
How/why is not this "user crashes system"? Kernel must not panic on OOM. There is memcg as well.