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: <20220816115614.GB27428@duo.ucw.cz>
Date:   Tue, 16 Aug 2022 13:56:14 +0200
From:   Pavel Machek <pavel@...x.de>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Steven Rostedt <rostedt@...dmis.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, pavel@...x.de,
        jonathanh@...dia.com, f.fainelli@...il.com,
        sudipm.mukherjee@...il.com, slade@...dewatkins.com
Subject: Big load on lkml created by -stable patchbombs was Re: [PATCH 5.19
 0000/1157] 5.19.2-rc1 review

Hi!

> > > This is the start of the stable review cycle for the 5.19.2 release.
> > > There are 1157 patches in this series, all will be posted as a response
> > > to this one.  If anyone has any issues with these being applied, please
> > > let me know.
> > 
> > Hi Greg,
> > 
> > Perhaps its time that you just send a single email to LKML pointing where to
> > find the stable releases. These patch bombs are bringing vger down to its
> > knees, and causing delays in people's workflows. This doesn't just affect
> > LKML, but all other vger mailing lists. Probably because LKML has the biggest
> > subscriber base that patch bombs to it can slow everything else down.
> > 
> > I sent 3 patches to the linux-trace-devel list almost 4 hours ago, and they
> > still haven't shown up. I was going to point people to it tonight but it's now
> > going to have to wait till tomorrow.
> 
> Email is async, sometimes it takes longer than others to recieve
> messages.

Well, email is pretty fast most of the month.

> My "patch bombs" get sent out slow to the mail servers, there is work to
> fix up vger and move it over to the LF-managed infrastructure, perhaps
> work with the vger admins to help that effort out?

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.

Is not it ultimately for vger admins to decide what kind of load they
consider acceptable?

Would it make sense to somehow batch the messages, or perhaps to
modify patchbombing scripts to send patches "slowly" so that -stable
does not DoS other lkml users?

Actually, if the patch is same between multiple -stable releases
(which is rather common case) sending it just once tagged with "this
goes to 4.9, 4.14, 4.19 and 5.10" would both take less bandwidth and
make review easier. (But I see it may not be that easy).

Best regards,
								Pavel
								
PS: ...who is currently on EDGE connection. LF-managed infrastructure
is not going to help for people who use slow links to access lkml.
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

Download attachment "signature.asc" of type "application/pgp-signature" (196 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ