linux-kernel - Re: Big load on lkml created by -stable patchbombs was Re: [PATCH 5.19 0000/1157] 5.19.2-rc1 review

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: <20220816181058.3a3fb20d@gandalf.local.home>
Date:   Tue, 16 Aug 2022 18:10:58 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Pavel Machek <pavel@...x.de>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
        linux@...ck-us.net, shuah@...nel.org, patches@...nelci.org,
        lkft-triage@...ts.linaro.org, jonathanh@...dia.com,
        f.fainelli@...il.com, sudipm.mukherjee@...il.com,
        slade@...dewatkins.com,
        John 'Warthog9' Hawley <warthog9@...nel.org>
Subject: Re: Big load on lkml created by -stable patchbombs was Re: [PATCH
 5.19 0000/1157] 5.19.2-rc1 review

On Tue, 16 Aug 2022 13:56:14 +0200
Pavel Machek <pavel@...x.de> wrote:

> I'm pretty used to -stable patches going to l-k, so I got used to
> current workflow. OTOH ... -stable _is_ quite significant fraction of
> total lkml traffic, and I see how people may hate that.

The thing I hate is that this slows down the other mailing lists. It
doesn't just affect LKML. It affects *all* lists. Even the ones that just
get a dozen emails a day. But the emails that do come, are important.

Perhaps another answer is to dedicate the LKML emails to their own servers,
and let the other mailing lists run separately such that the patch bombs to
LKML do not affect any of the other lists.

That would be an acceptable solution for me ;-)

-- Steve