All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiayuan Chen <jiayuan.chen@linux.dev>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf] netfilter: nft_fib_ipv6: bail out of sibling walk if rt got unlinked
Date: Wed, 27 May 2026 13:18:32 +0800	[thread overview]
Message-ID: <796e346d-1975-47cd-b4f9-d7b67c3f010c@linux.dev> (raw)
In-Reply-To: <ahWrbTAdNIjo02D-@strlen.de>


On 5/26/26 10:17 PM, Florian Westphal wrote:
>> diff --git a/net/ipv6/netfilter/nft_fib_ipv6.c b/net/ipv6/netfilter/nft_fib_ipv6.c
>> index c0a0075e2590..2dbe44715df3 100644
>> --- a/net/ipv6/netfilter/nft_fib_ipv6.c
>> +++ b/net/ipv6/netfilter/nft_fib_ipv6.c
>> @@ -191,6 +191,9 @@ static bool nft_fib6_info_nh_uses_dev(struct fib6_info *rt,
>>   
>>   		if (nft_fib6_info_nh_dev_match(nh_dev, dev))
>>   			return true;
>> +
>> +		if (!READ_ONCE(rt->fib6_nsiblings))
>> +			return false;
>>   	}
> This time sashiko points to same bug pattern in rt6_fill_node:
>
> This is a pre-existing issue, but does rt6_fill_node() also need this
> detach check to prevent the same infinite loop?
>
> https://sashiko.dev/#/patchset/20260526020227.4857-1-jiayuan.chen%40linux.dev
>
> (No need to resend this patch, but maybe you have cycles to fix the
>   other spot too)



Hi Florian,

Thanks for the heads-up. After auditing the rest of net/ipv6/route.c
I noticed fib6_select_path() seems to have the same pattern as well
(walks &first->fib6_siblings under RCU with no inside-loop bail-out).

I'll send fixes for both spots directly against net.

Thanks,
Jiayuan


      reply	other threads:[~2026-05-27  5:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26  2:02 [PATCH nf] netfilter: nft_fib_ipv6: bail out of sibling walk if rt got unlinked Jiayuan Chen
2026-05-26 14:17 ` Florian Westphal
2026-05-27  5:18   ` Jiayuan Chen [this message]

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=796e346d-1975-47cd-b4f9-d7b67c3f010c@linux.dev \
    --to=jiayuan.chen@linux.dev \
    --cc=fw@strlen.de \
    --cc=netfilter-devel@vger.kernel.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 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.