All of lore.kernel.org
 help / color / mirror / Atom feed
From: 성병찬 <tjdqudcks0424@naver.com>
To: <netdev-bot+sinfo@kernel.org>
Cc: "Sabrina Dubroca" <sd@queasysnail.net>, netdev@vger.kernel.org
Subject: Re: [PATCH net] macsec: reject replays after non-XPN receive PN exhaustion
Date: Thu, 08 Oct 2026 17:39:20 +0900	[thread overview]
Message-ID: <71b4df326a3a2df681a58ac37f5bb49f@cweb016.nm> (raw)
In-Reply-To: <179144821519.2527009.9630064777060740854@kernel.org>

Hi,

This issue was identified during manual static source review of the
non-XPN receive PN exhaustion and replay-checking paths, with assistance
from OpenAI Codex.

I subsequently reproduced and validated it using a local veth pair and
the production software MACsec receive path. The identical authenticated
PN U32_MAX frame was delivered twice in all three baseline runs. With the
patch applied, the replay was rejected in all three runs, while the
PN max-1, fresh terminal-frame, and bad-ICV controls retained their
expected behavior.

Thanks,
Sung Byeongchan

  reply	other threads:[~2026-10-08  8:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08  8:25 [PATCH net] macsec: reject replays after non-XPN receive PN exhaustion Sung Byeongchan
2026-10-08  8:30 ` netdev-bot+sinfo
2026-10-08  8:39   ` 성병찬 [this message]
2026-10-08 16:35 ` Sabrina Dubroca

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=71b4df326a3a2df681a58ac37f5bb49f@cweb016.nm \
    --to=tjdqudcks0424@naver.com \
    --cc=netdev-bot+sinfo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sd@queasysnail.net \
    /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.