linux-kernel - Re: [PATCH] x86/hyperv: Use atomic_try_cmpxchg() to micro-optimize hv_nmi

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

Message-ID: <ddeefd4d0323df0948565fea2ffb55793fdcc8dc@linux.dev>
Date:   Wed, 22 Nov 2023 16:52:43 +0000
From:   "Konstantin Ryabitsev" <konstantin.ryabitsev@...ux.dev>
To:     "Wei Liu" <wei.liu@...nel.org>, "Uros Bizjak" <ubizjak@...il.com>
Cc:     linux-hyperv@...r.kernel.org, linux-kernel@...r.kernel.org,
        tools@...ux.kernel.org
Subject: Re: [PATCH] x86/hyperv: Use atomic_try_cmpxchg() to micro-optimize
 hv_nmi_unknown()

November 21, 2023 at 10:51 PM, "Wei Liu" <wei.liu@...nel.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