linux-kernel - Re: [PATCH] serial/pmac_zilog: Remove flawed mitigation for rx irq flood

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]

Date: Thu, 4 Apr 2024 12:20:56 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Jiri Slaby <jirislaby@...nel.org>
Cc: Finn Thain <fthain@...ux-m68k.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, 
	Benjamin Herrenschmidt <benh@...nel.crashing.org>, Michael Ellerman <mpe@...erman.id.au>, 
	Nicholas Piggin <npiggin@...il.com>, Christophe Leroy <christophe.leroy@...roup.eu>, 
	"Aneesh Kumar K.V" <aneesh.kumar@...nel.org>, "Naveen N. Rao" <naveen.n.rao@...ux.ibm.com>, 
	linux-m68k@...ts.linux-m68k.org, linux-kernel@...r.kernel.org, 
	linux-serial@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org
Subject: Re: [PATCH] serial/pmac_zilog: Remove flawed mitigation for rx irq flood

On Thu, Apr 4, 2024 at 8:07 AM Jiri Slaby <jirislaby@...nel.org> wrote:
> On 04. 04. 24, 0:29, Andy Shevchenko wrote:

> >> Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>
> >> Cc: Michael Ellerman <mpe@...erman.id.au>
> >> Cc: Nicholas Piggin <npiggin@...il.com>
> >> Cc: Christophe Leroy <christophe.leroy@...roup.eu>
> >> Cc: "Aneesh Kumar K.V" <aneesh.kumar@...nel.org>
> >> Cc: "Naveen N. Rao" <naveen.n.rao@...ux.ibm.com>
> >> Cc: linux-m68k@...ts.linux-m68k.org
> >
> > Second, please move these Cc to be after the '---' line
>
> Sorry, but why?

Really need to create a Q&A entry for this.

This will pollute the commit messages with irrelevant (to some extent)
information. Since we have a lore mail archive there is no need to
have this (the email itself will be sent to the list of people,
otherwise the Cc email headers can be tracked in the mail archive).
Also note, some developers may read git history on the mobile devices,
meaning small screens, this just (as for backtraces) simply blurs the
information with a high potential to lose significant piece(s) of
information). Last, but not least is environmentally friendly approach
(I'm not joking): having it on thousands of computers, scrolling with
longer time, power for compressing - decompressing -- all of this
wastes a lot of energy (maybe kWh:s per such a Cc list).

-- 
With Best Regards,
Andy Shevchenko