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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACT4Y+YL1zCXp23NROvkry-WjPYTLbbduM5Mnwn1JJd6Bi9_PQ@mail.gmail.com>
Date:   Mon, 11 May 2020 17:29:35 +0200
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Qian Cai <cai@....pw>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Peter Xu <peterx@...hat.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Linux-MM <linux-mm@...ck.org>, Jens Axboe <axboe@...nel.dk>,
        Christoph Lameter <cl@...ux.com>,
        Johannes Weiner <hannes@...xchg.org>,
        syzkaller <syzkaller@...glegroups.com>,
        Dan Rue <dan.rue@...aro.org>
Subject: Re: [PATCH 0/2] mm: Two small fixes for recent syzbot reports

On Thu, Apr 16, 2020 at 2:34 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi Dmitry,
>
> On Tue, 14 Apr 2020 13:12:50 +0200 Dmitry Vyukov <dvyukov@...gle.com> wrote:
> >
> > AI: we need to CC linux-next@ on linux-next build/boot failures. I
> > will work on this.
> > We have functionality to CC given emails on _all_ bugs on the given
> > tree, but we don't have this for build/boot bugs only. I will try to
> > add this soon.
> > Stephen, do you want to be CCed as well? Or just linux-next@?
>
> Please cc me as well, thanks.

To close the loop: I implemented and deployed 2 improvements:

1. Notion of per-repo "build maintainers":
https://github.com/google/syzkaller/commit/88cb3e92ba25303ab67aaceb083fe7304fccd32f
Now linux-next@ and Stephen should be CCed on all linux-next breakages
automatically.

2. Finding maintainers for build errors:
https://github.com/google/syzkaller/commit/65a44e22ba217ef7272b9d3735e9d12cfaa204f6
syzbot will attempt to extract the broken file name from make output
and then run get_matainers.pl on it to find relevant emails.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ