From: Eric Biggers <ebiggers@kernel.org>
To: Andrea Mayer <andrea.mayer@uniroma2.it>
Cc: netdev@vger.kernel.org, David Lebrun <dlebrun@google.com>,
stable@vger.kernel.org, stefano.salsano@uniroma2.it,
Paolo Lungaroni <paolo.lungaroni@uniroma2.it>
Subject: Re: [PATCH net-next 1/3] ipv6: sr: Fix MAC comparison to be constant-time
Date: Mon, 18 Aug 2025 13:30:22 -0700 [thread overview]
Message-ID: <20250818203022.GA1305@sol> (raw)
In-Reply-To: <20250818193849.GB12939@google.com>
On Mon, Aug 18, 2025 at 07:38:52PM +0000, Eric Biggers wrote:
> On Mon, Aug 18, 2025 at 09:16:07PM +0200, Andrea Mayer wrote:
> > On Fri, 15 Aug 2025 20:11:34 -0700
> > Eric Biggers <ebiggers@kernel.org> wrote:
> >
> > > To prevent timing attacks, MACs need to be compared in constant time.
> > > Use the appropriate helper function for this.
> > >
> > > Fixes: bf355b8d2c30 ("ipv6: sr: add core files for SR HMAC support")
> > > Cc: stable@vger.kernel.org
> > > Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> > > ---
> > > net/ipv6/seg6_hmac.c | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> >
> > Hi Eric,
> >
> > Thanks for the fix!
> >
> > I believe it would be best to submit this fix separately from the current patch
> > set. Since this addresses a bug rather than an enhancement or cleanup, sending
> > it individually with the 'net' tag will help facilitate applying this patch to
> > the net tree.
> >
> > Ciao,
> > Andrea
>
> Then there would be a merge conflict between the two patchsets.
>
> I can do that if you want, but then I'd probably have to wait for this
> patch to reach net-next before the rest can proceed.
I guess patches 2 and 3 have to wait for "ipv6: sr: validate HMAC
algorithm ID in seg6_hmac_info_add" anyway, as they conflict with that
too. Okay, I resent patch 1 as a standalone patch targeting "net":
https://lore.kernel.org/netdev/20250818202724.15713-1-ebiggers@kernel.org/
- Eric
next prev parent reply other threads:[~2025-08-18 20:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-16 3:11 [PATCH net-next 0/3] ipv6: sr: HMAC fix and cleanups Eric Biggers
2025-08-16 3:11 ` [PATCH net-next 1/3] ipv6: sr: Fix MAC comparison to be constant-time Eric Biggers
2025-08-18 19:16 ` Andrea Mayer
2025-08-18 19:38 ` Eric Biggers
2025-08-18 20:30 ` Eric Biggers [this message]
2025-08-16 3:11 ` [PATCH net-next 2/3] ipv6: sr: Use HMAC-SHA1 and HMAC-SHA256 library functions Eric Biggers
2025-08-16 7:01 ` Kuniyuki Iwashima
2025-08-16 7:26 ` Eric Biggers
2025-08-17 16:58 ` Ido Schimmel
2025-08-16 3:11 ` [PATCH net-next 3/3] ipv6: sr: Prepare HMAC key ahead of time Eric Biggers
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=20250818203022.GA1305@sol \
--to=ebiggers@kernel.org \
--cc=andrea.mayer@uniroma2.it \
--cc=dlebrun@google.com \
--cc=netdev@vger.kernel.org \
--cc=paolo.lungaroni@uniroma2.it \
--cc=stable@vger.kernel.org \
--cc=stefano.salsano@uniroma2.it \
/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