linux-kernel - Re: linux-next boot error (2)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACT4Y+boXfNjHT1M5B6OttHiUFKsvL7AFH2Gfd+DbkNoQD4YVg@mail.gmail.com>
Date:   Wed, 21 Nov 2018 14:32:43 +0100
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     David Howells <dhowells@...hat.com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        syzbot <syzbot+762a577f56cfb1574647@...kaller.appspotmail.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        "Levin, Alexander" <alexander.levin@...izon.com>,
        LKML <linux-kernel@...r.kernel.org>, linux@...inikbrodowski.net,
        Luc Van Oostenryck <luc.vanoostenryck@...il.com>,
        nikolaus.voss@...wensteinmedical.de,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: linux-next boot error (2)

On Tue, Sep 11, 2018 at 11:24 PM, David Howells <dhowells@...hat.com> wrote:
> Stephen Rothwell <sfr@...b.auug.org.au> 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