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

Date:   Wed, 20 Oct 2021 06:10:22 -1000
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     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 Tue, Oct 19, 2021 at 3:13 AM Steven Rostedt <rostedt@...dmis.org> wrote:
>
> tracing recursion fix:

I've pulled this, but the commit in question shows that you are doing
something wrong in your workflow.

In particular, you seem to have cut-and-pasted email names from some
raw email, and done so incorrectly.

As a result, we have this:

    Cc: =?utf-8?b?546L6LSH?= <yun.wang@...ux.alibaba.com>

which is not a valid name for Yun.

It should have been

    Cc: 王贇 <yun.wang@...ux.alibaba.com>

Either let the email tools do proper decoding of the headers and
cut-and-paste from that, or use one of the explicit tools that do
email header decoding (there's at least a few online ones).

Yeah, yeah, I know, we're much too used to US-ASCII (or, in my case,
the slightly expanded Western Latin1), and there's a couple of other
examples of this in the git history, but we really should strive to
get peoples names right.

                    Linus