linux-kernel - Re: [GIT PULL] tracing: Fix to recursion protection for 5.15

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] [day] [month] [year] [list]

Date:   Wed, 20 Oct 2021 23:36:47 -0700
From:   Joe Perches <joe@...ches.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Steven Rostedt <rostedt@...dmis.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Petr Mladek <pmladek@...e.com>,
        Peter Zijlstra <peterz@...radead.org>
Subject: Re: [GIT PULL] tracing: Fix to recursion protection for 5.15

On Wed, 2021-10-20 at 20:27 -1000, Linus Torvalds wrote:
> On Wed, Oct 20, 2021 at 8:16 PM Joe Perches <joe@...ches.com> wrote:
> > 
> > Generally, a tool like b4 should be able to create a list of any
> > email addresses in a thread linked commit.
> 
> I really think Cc lines are very useful.
> 
> That said, they are *more* useful when they are thought about, than
> when they are automated.
[]
> I will, for example, strive to put the people who _participated_ in
> some discussion as the "Cc" list - they may not have acked a patch, or
> reviewed it, but they might have piped up in the discussion, and that
> probably merits them then knowing about any problems it causes.

Which is exactly what "thread linked commit" attempted to convey.