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] [day] [month] [year] [list]

Date:   Tue, 27 Nov 2018 11:38:47 +0100
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     David Howells <dhowells@...hat.com>
Cc:     Al Viro <viro@...iv.linux.org.uk>,
        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, Nov 27, 2018 at 11:25 AM, David Howells <dhowells@...hat.com> wrote:
> Dmitry Vyukov <dvyukov@...gle.com> 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 he's carrying the patches
> now.


A similar case in linux-next was discussed recently:
https://groups.google.com/d/msg/syzkaller-bugs/xiSF9GdiikU/uBoyYyf3AQAJ
For such cases it can make more sense to use Tested-by tag instead of
Reported-by to not confuse people that the resulting amended patch
fixes some bug (e.g. stable will try to pick it up).  Tested-by is
also recognized by syzbot.