From: Tomeu Vizoso <tomeu.vizoso@collabora.com>
To: Konstantin Ryabitsev <konstantin.ryabitsev@linux.dev>,
Chuck Lever III <chuck.lever@oracle.com>,
Muhammad Usama Anjum <usama.anjum@collabora.com>
Cc: Bruce Fields <bfields@fieldses.org>,
Vasily Averin <vvs@virtuozzo.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
kernel@collabora.com, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] nfs: check nf pointer for validity before use
Date: Wed, 22 Dec 2021 07:06:05 +0100 [thread overview]
Message-ID: <68222978-eb24-cf94-9fb5-4421cbb2b2c8@collabora.com> (raw)
In-Reply-To: <f8459dd30802e4da915c63f6b70263e6@linux.dev>
On 12/21/21 11:18 PM, Konstantin Ryabitsev wrote:
> December 21, 2021 3:00 PM, "Chuck Lever III" <chuck.lever@oracle.com> wrote:
>> Btw, b4 complained about collabora.com's DKIM:
>>
>> [cel@bazille linux]$ b4 am
>> https://lore.kernel.org/linux-nfs/YcIjJ4jN3ax1rqaE@debian-BULLSEYE-live-builder-AMD64/raw
>> Grabbing thread from
>> lore.kernel.org/linux-nfs/YcIjJ4jN3ax1rqaE%40debian-BULLSEYE-live-builder-AMD64/t.mbox.gz
>> Analyzing 1 messages in the thread
>> Checking attestation on all messages, may take a moment...
>> ---
>> ✗ [PATCH] nfs: check nf pointer for validity before use
>> ---
>> ✗ BADSIG: DKIM/collabora.com
>
> This is because collabora.com has DKIM canonicalization configured as "c=simple/simple". See my previous message to intel.com for why this should be changed to c=relaxed/simple:
>
> https://lore.kernel.org/lkml/20211214150032.nioelgvmase7yyus@meerkat.local/
Thank you both, Chuck and Konstantin,
I have forwarded this conversation to our sysadmin team.
Best regards,
Tomeu
prev parent reply other threads:[~2021-12-22 6:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 18:55 Muhammad Usama Anjum
2021-12-21 20:00 ` Chuck Lever III
2021-12-21 22:18 ` Konstantin Ryabitsev
2021-12-22 6:06 ` Tomeu Vizoso [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=68222978-eb24-cf94-9fb5-4421cbb2b2c8@collabora.com \
--to=tomeu.vizoso@collabora.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=konstantin.ryabitsev@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=usama.anjum@collabora.com \
--cc=vvs@virtuozzo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®