netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Justin Iurman <justin.iurman@uliege.be>
Cc: Paolo Abeni <pabeni@redhat.com>,
	davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	andrew+netdev@lunn.ch, horms@kernel.org, dsahern@kernel.org
Subject: Re: [PATCH net v2 2/2] net: ipv6: fix dst ref loops in rpl, seg6 and ioam6 lwtunnels
Date: Sat, 1 Feb 2025 16:56:58 -0800	[thread overview]
Message-ID: <20250201165658.707c5d9d@kernel.org> (raw)
In-Reply-To: <4b8d9c6e-cbe6-4c75-b709-c732db0cf331@uliege.be>

On Sat, 1 Feb 2025 14:52:05 +0100 Justin Iurman wrote:
> >> ioam6.sh already triggers the looped cases in both inline and encap
> >> tests. Not sure about seg6 though, and there is no selftest for rpl.  
> > 
> > Right! To be clear I meant just for seg6 and rpl. The ioam6 test
> > is clearly paying off, thanks for putting in the work there! :)  
> 
> Got it. Of course, I'll see what I can do. And glad the ioam6 selftest 
> helped :-) Not sure what the current SRv6 selftests are doing though, 
> but it looks like the "looped cases" were not caught. Probably because 
> the first segment makes it so that the new dst_entry is not the same as 
> the origin (I'll have to double check). I could just add a test with a 
> route matching on a subnet, so that the next segment matches too (i.e., 
> old dst == new dst). Overall, both seg6 and rpl selftests to detect the 
> looped cases would look like "dummy" tests, i.e., useless without 
> kmemleak. Does it sound OK?

Yes, tests written purely for code coverage are perfectly acceptable.
Let alone when they cover paths which where buggy in the past.

FWIW my series was applied now, in case you were waiting.

  reply	other threads:[~2025-02-02  0:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-30  3:15 [PATCH net v2 1/2] net: ipv6: fix dst refleaks in rpl, seg6 and ioam6 lwtunnels Jakub Kicinski
2025-01-30  3:15 ` [PATCH net v2 2/2] net: ipv6: fix dst ref loops " Jakub Kicinski
2025-01-30 10:28   ` Simon Horman
2025-01-30 13:41     ` Justin Iurman
2025-01-30 14:56       ` Jakub Kicinski
2025-01-30 15:35         ` Simon Horman
2025-01-30 11:34   ` Paolo Abeni
2025-01-30 13:52     ` Justin Iurman
2025-01-30 14:55       ` Jakub Kicinski
2025-01-30 15:12         ` Justin Iurman
2025-01-30 16:53           ` Jakub Kicinski
2025-02-01 13:52             ` Justin Iurman
2025-02-02  0:56               ` Jakub Kicinski [this message]
2025-01-30 10:23 ` [PATCH net v2 1/2] net: ipv6: fix dst refleaks " Simon Horman
2025-02-02  1:00 ` patchwork-bot+netdevbpf

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=20250201165658.707c5d9d@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=justin.iurman@uliege.be \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).