From: "Konstantin Ryabitsev" <konstantin.ryabitsev@linux.dev>
To: "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: Tue, 21 Dec 2021 22:18:34 +0000 [thread overview]
Message-ID: <f8459dd30802e4da915c63f6b70263e6@linux.dev> (raw)
In-Reply-To: <05877B02-900A-4B22-9460-D2F0D20931DC@oracle.com>
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/
Hope this helps.
-K
next prev parent reply other threads:[~2021-12-21 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 18:55 [PATCH] nfs: check nf pointer for validity before use Muhammad Usama Anjum
2021-12-21 20:00 ` Chuck Lever III
2021-12-21 22:18 ` Konstantin Ryabitsev [this message]
2021-12-22 6:06 ` Tomeu Vizoso
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=f8459dd30802e4da915c63f6b70263e6@linux.dev \
--to=konstantin.ryabitsev@linux.dev \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@collabora.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.