Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 11 Aug 2021 16:28:19 -0400
From:   Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To:     Kees Cook <keescook@chromium.org>
Cc:     Elliot Berman <quic_eberman@quicinc.com>,
        Sami Tolvanen <samitolvanen@google.com>,
        linux-kernel@vger.kernel.org, Jinlong Mao <jinlmao@codeaurora.org>
Subject: Re: [PATCH 1/1] cfi: Use rcu_read_{un}lock_sched_notrace
Message-ID: <20210811202819.u5p67vjzkdgcjzxk@nitro.local>
References: <20210811155914.19550-1-quic_eberman@quicinc.com>
 <202108111306.527943F39@keescook>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <202108111306.527943F39@keescook>
Precedence: bulk

On Wed, Aug 11, 2021 at 01:10:36PM -0700, Kees Cook wrote:
> Do you know if qualcomm is mangling outbound emails? (i.e. was the
> trailing body suffix added after calculating the DKIM signature?)

This may not be the case -- the DKIM signature uses "simple/simple"
normalization, meaning that all headers are preserved wrt upper/lowercase and
whitespace. These tend to not survive mailing list managers, unfortunately.

Kees, if you still have the copy that arrived straight at your chromium.org
address (not via vger), you can diff it with what you get from lore to see
where the culprit is.

-K