Re: linux-next boot error (2)

[Dmitry Vyukov]

On Tue, Sep 11, 2018 at 11:24 PM, David Howells <dhowells@xxxxxxxxxx> wrote:
> Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> 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 bug is still considered
open:
https://syzkaller.appspot.com/bug?extid=762a577f56cfb1574647
10 days ago linux-next become broken for another reason, but syzbot
did not report a new bug because the previous one is still open (new
reports are merged into the existing open bug).

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:

#syz fix: apparmor: Implement security hooks for the new mount API

Also helps to keep dashboard relevant:
https://syzkaller.appspot.com/#upstream-open
a pile of hundreds of stale bugs is not too useful, and losing half of
bug reports in LKML archives is not good too.

Thanks in advance