All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Konstantin Ryabitsev" <konstantin.ryabitsev@linux.dev>
To: "Wei Liu" <wei.liu@kernel.org>, "Uros Bizjak" <ubizjak@gmail.com>
Cc: linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
	tools@linux.kernel.org
Subject: Re: [PATCH] x86/hyperv: Use atomic_try_cmpxchg() to micro-optimize hv_nmi_unknown()
Date: Wed, 22 Nov 2023 16:52:43 +0000	[thread overview]
Message-ID: <ddeefd4d0323df0948565fea2ffb55793fdcc8dc@linux.dev> (raw)
In-Reply-To: <ZV163ePuUQyyeKUj@liuwe-devbox-debian-v2>

November 21, 2023 at 10:51 PM, "Wei Liu" <wei.liu@kernel.org> wrote:
> Uros, just so you know, DKIM verification failed when I used b4 to apply
> this patch. You may want to check your email setup.

This is not actually Uros's fault. Recently, Gmail started adding a forced expiration field to their DKIM signatures, via the x= field:

    DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20230601; t=1699981249; x=1700586049; darn=vger.kernel.org;
                                               ^^^^^^^^^^^^^

This gives the signature an enforced validity of only 7 days. Since the original message was sent on November 14 and you're retrieving it on November 21, this causes the DKIM check to fail.

I need to figure out how to make b4 ignore the x= field, because it's not relevant for our purposes, but the library we're using for DKIM doesn't currently have any mechanism to do so. I will open an RFE with them in the hopes that we can get this implemented.

Regards,
-K

      parent reply	other threads:[~2023-11-22 16:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14 16:59 [PATCH] x86/hyperv: Use atomic_try_cmpxchg() to micro-optimize hv_nmi_unknown() Uros Bizjak
2023-11-15 17:19 ` Michael Kelley
2023-11-15 20:58   ` Uros Bizjak
2023-11-22  3:51     ` Wei Liu
2023-11-22 12:31       ` Uros Bizjak
2023-11-22 12:38         ` Uros Bizjak
2023-11-22 16:52       ` Konstantin Ryabitsev [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=ddeefd4d0323df0948565fea2ffb55793fdcc8dc@linux.dev \
    --to=konstantin.ryabitsev@linux.dev \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tools@linux.kernel.org \
    --cc=ubizjak@gmail.com \
    --cc=wei.liu@kernel.org \
    /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.