Re: linux-next boot error (2)

2018-11-27 Thread Dmitry Vyukov
On Tue, Nov 27, 2018 at 11:25 AM, David Howells wrote: > Dmitry Vyukov wrote: > >> Please either use the Reported-by tag (for amended linux-next fixes >> Tested-by can make more sense and is recognized too), or tell syzbot >> separately: > > It got folded in as that's better than carrying a

Re: linux-next boot error (2)

2018-11-27 Thread Dmitry Vyukov
On Tue, Nov 27, 2018 at 11:25 AM, David Howells wrote: > Dmitry Vyukov wrote: > >> Please either use the Reported-by tag (for amended linux-next fixes >> Tested-by can make more sense and is recognized too), or tell syzbot >> separately: > > It got folded in as that's better than carrying a

Re: linux-next boot error (2)

2018-11-27 Thread David Howells
Dmitry Vyukov wrote: > Please either use the Reported-by tag (for amended linux-next fixes > Tested-by can make more sense and is recognized too), or tell syzbot > separately: It got folded in as that's better than carrying a separate patch. I'll ask Al how he wants to deal with this since

Re: linux-next boot error (2)

2018-11-27 Thread David Howells
Dmitry Vyukov wrote: > Please either use the Reported-by tag (for amended linux-next fixes > Tested-by can make more sense and is recognized too), or tell syzbot > separately: It got folded in as that's better than carrying a separate patch. I'll ask Al how he wants to deal with this since

Re: linux-next boot error (2)

2018-11-21 Thread Dmitry Vyukov
On Tue, Sep 11, 2018 at 11:24 PM, David Howells wrote: > Stephen Rothwell wrote: > >> I will apply this fix until the proper fix arrives in the vfs tree: > > Thanks. > > David This was fixed in September, but the Reported-by tag wasn't added and nobody told syzbot that this is fixed. So the

Re: linux-next boot error (2)

2018-11-21 Thread Dmitry Vyukov
On Tue, Sep 11, 2018 at 11:24 PM, David Howells wrote: > Stephen Rothwell wrote: > >> I will apply this fix until the proper fix arrives in the vfs tree: > > Thanks. > > David This was fixed in September, but the Reported-by tag wasn't added and nobody told syzbot that this is fixed. So the

Re: linux-next boot error (2)

2018-09-11 Thread David Howells
Stephen Rothwell wrote: > I will apply this fix until the proper fix arrives in the vfs tree: Thanks. David

Re: linux-next boot error (2)

2018-09-11 Thread David Howells
Stephen Rothwell wrote: > I will apply this fix until the proper fix arrives in the vfs tree: Thanks. David

Re: linux-next boot error (2)

2018-09-11 Thread Stephen Rothwell
Hi David, On Tue, 11 Sep 2018 21:16:27 +0100 David Howells wrote: > > Andrei Vagin spotted a missing change to apparmor: > apparmor_fs_context_parse_param() needs to return -ENOPARAM, not 0. I will apply this fix until the proper fix arrives in the vfs tree: From: Stephen Rothwell Date: Wed,

Re: linux-next boot error (2)

2018-09-11 Thread Stephen Rothwell
Hi David, On Tue, 11 Sep 2018 21:16:27 +0100 David Howells wrote: > > Andrei Vagin spotted a missing change to apparmor: > apparmor_fs_context_parse_param() needs to return -ENOPARAM, not 0. I will apply this fix until the proper fix arrives in the vfs tree: From: Stephen Rothwell Date: Wed,

Re: linux-next boot error (2)

2018-09-11 Thread David Howells
Andrei Vagin spotted a missing change to apparmor: apparmor_fs_context_parse_param() needs to return -ENOPARAM, not 0. David

Re: linux-next boot error (2)

2018-09-11 Thread David Howells
Andrei Vagin spotted a missing change to apparmor: apparmor_fs_context_parse_param() needs to return -ENOPARAM, not 0. David

Re: linux-next boot error (2)

2018-09-06 Thread Dmitry Vyukov
On Thu, Sep 6, 2018 at 10:41 AM, David Howells wrote: > Do we know what type of filesystem is on the root device? ext4 The image is built with this script (you can find mkfs.ext4 there): https://github.com/google/syzkaller/blob/master/tools/create-gce-image.sh > Also, is there a way to tell if

Re: linux-next boot error (2)

2018-09-06 Thread Dmitry Vyukov
On Thu, Sep 6, 2018 at 10:41 AM, David Howells wrote: > Do we know what type of filesystem is on the root device? ext4 The image is built with this script (you can find mkfs.ext4 there): https://github.com/google/syzkaller/blob/master/tools/create-gce-image.sh > Also, is there a way to tell if

Re: linux-next boot error (2)

2018-09-06 Thread David Howells
Do we know what type of filesystem is on the root device? Also, is there a way to tell if AppArmor denied something? David

Re: linux-next boot error (2)

2018-09-06 Thread David Howells
Do we know what type of filesystem is on the root device? Also, is there a way to tell if AppArmor denied something? David

linux-next boot error (2)

2018-09-06 Thread syzbot
Hello, syzbot found the following crash on: HEAD commit:509d1f0c294a Add linux-next specific files for 20180906 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=157b857a40 kernel config: https://syzkaller.appspot.com/x/.config?x=d1a648893bbc933

linux-next boot error (2)

2018-09-06 Thread syzbot
Hello, syzbot found the following crash on: HEAD commit:509d1f0c294a Add linux-next specific files for 20180906 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=157b857a40 kernel config: https://syzkaller.appspot.com/x/.config?x=d1a648893bbc933