linux-kernel - 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: <20220816080452.400d1adc@gandalf.local.home>
Date:   Tue, 16 Aug 2022 08:04:52 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     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: Re: [PATCH 5.19 0000/1157] 5.19.2-rc1 review

On Tue, 16 Aug 2022 07:17:36 +0200
Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
> > 
> > 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.

The delays always happen when you do these patch bombs. In fact, that's
how I knew you sent them just now. My patches finally arrived, just under 8
hours since I sent them!

> 
> 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 not sure what I can do to help out. I'm not a very good email admin.
(I'm struggling to fix my wife's email now).

> 
> > I really do not think LKML needs to see all 1157 patches that are being
> > backported. There's other places to send them that will not be as disruptive.  
> 
> And where would that be?

You already Cc stable@...r.kernel.org. Does lore track that?

My point is, LKML has what, 10,000 subscribers? Maybe only 5000? Even at
5000, probably at most 50 subscribers look at the stable patches (and I'm
being optimistic). That means, these 3000 emails go to 4950 people that
will never look at them. That's 14,850,000 emails that are wasting disk
space, CPU cycles and electricity. Think of the environment :-)

> 
> Getting the patches out for review is good, and necessary.  Patches
> should never be considered "noise" as it is what we are doing here.  If
> we have infrastructure issues handling these messages, we should work to
> resolve them as really, 3000 emails should not be a lot to manage,
> unless you are being throttled by your email provider?

I'm not saying that they should not be sent out. I'm asking, do they need
to be sent out to the list with the most subscribers? You already
(rightfully) Cc the maintainers of the patches. Since they already go to
the stable list, and if lore archives them, then you could just send a link
to LKML to the lore patch set. Then people could still review them.

Do those that review these patches really just read LKML to do so?

Or is this the spam approach of sending out to 1000x more than you need to,
just so that you get a few more eyes?

And the issue I have with this, is that it affects *all* mailing list on
vger not just LKML. I don't read LKML anymore, but I do read the smaller
lists. And blocking emails for 8 hours to these lists does have an effect on
productivity.

-- Steve