mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@nvidia.com>
To: Lawrence Lee <lfqlee314@gmail.com>
Cc: David Ahern <dsahern@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	netdev@vger.kernel.org, Arun Ajith S <aajith@arista.com>,
	Roopa Prabhu <roopa@nvidia.com>,
	Jaehee Park <jhpark1013@gmail.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Shuah Khan <shuah@kernel.org>,
	linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 2/2] selftests: net: test untracked NA recovery of FAILED neighbors
Date: Wed, 23 Sep 2026 11:36:33 +0300	[thread overview]
Message-ID: <20260923083633.GA2626135@shredder> (raw)
In-Reply-To: <ce40008682ed26ab039168a5fcb515eff8d30c3a.1790127207.git.lfqlee314@gmail.com>

On Wed, Sep 23, 2026 at 01:34:19AM +0000, Lawrence Lee wrote:
> Seed a FAILED neighbor before triggering an unsolicited NA. Verify that
> the entry transitions to STALE and learns the advertised link-layer
> address only when drop_unsolicited_na is disabled, accept_untracked_na
> mode 1 or in-prefix mode 2 is enabled, and IPv6 forwarding is enabled.
> Verify that disabling each gate keeps the entry in FAILED without a
> link-layer address.
> 
> Mark the seed externally learned and disable carrier-based eviction so
> the entry cannot be garbage-collected before the NA arrives. Require the
> marker after processing to prove that a recovered entry was updated in
> place instead of deleted and recreated.
> 
> Keep the NA source, target, and neighbor key fixed for the mode 2 cases.
> Vary the prefix configured on the router to exercise the source-prefix
> check without changing the entry under test.
> 
> Arm packet capture before bringing up the host interface and starting
> DAD. Wait for the capture to become ready and for tcpdump to exit so the
> NA cannot be missed and receive processing is complete before checking
> the neighbor entry.
> 
> Preserve the return code from test_unsolicited_na_common() before
> constructing the test description. The array assignment previously reset
> the return code to zero and caused existing cases to report false success.
> 
> Fixes: f9a2fb73318e ("net/ipv6: Introduce accept_unsolicited_na knob to implement router-side changes for RFC9131")

You shouldn't have added a Fixes tag. Backporting this patch to older
kernels will make the test fail. Wait for feedback from Jakub / Paolo
before posting v5. They might agree to strip it before applying.

> Link: https://lore.kernel.org/r/20260813233344.445265-1-lfqlee314@gmail.com
> Assisted-by: LLM Sashiko sparse
> Signed-off-by: Lawrence Lee <lfqlee314@gmail.com>

  reply	other threads:[~2026-09-23  8:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23  1:34 [PATCH net-next v4 0/2] ipv6: update NUD_FAILED neighbors from NA messages Lawrence Lee
2026-09-23  1:34 ` [PATCH net-next v4 1/2] " Lawrence Lee
2026-09-23  1:34 ` [PATCH net-next v4 2/2] selftests: net: test untracked NA recovery of FAILED neighbors Lawrence Lee
2026-09-23  8:36   ` Ido Schimmel [this message]
2026-09-23 17:49     ` Lawrence Lee

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=20260923083633.GA2626135@shredder \
    --to=idosch@nvidia.com \
    --cc=aajith@arista.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jhpark1013@gmail.com \
    --cc=kuba@kernel.org \
    --cc=lfqlee314@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=roopa@nvidia.com \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®