Linux kernel -stable discussions
 help / color / mirror / Atom feed
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 19:38:49 +0000	[thread overview]
Message-ID: <20250818193849.GB12939@google.com> (raw)
In-Reply-To: <20250818211607.c8eb87fbac2f81774022b54b@uniroma2.it>

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.

- Eric

  reply	other threads:[~2025-08-18 19:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250816031136.482400-1-ebiggers@kernel.org>
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 [this message]
2025-08-18 20:30       ` 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=20250818193849.GB12939@google.com \
    --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