mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linkui Xiao <xiaolinkui@126.com>
To: Eric Dumazet <edumazet@google.com>,
	Kuniyuki Iwashima <kuniyu@google.com>,
	Willem de Bruijn <willemb@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, idosch@nvidia.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, Linkui Xiao <xiaolinkui@kylinos.cn>
Subject: Re: [PATCH] ipv4: fib: annotate data-race around nh->nh_saddr
Date: Tue, 15 Sep 2026 10:36:58 +0800	[thread overview]
Message-ID: <182acfbd-d03a-4847-8fb8-4d0d29f22107@126.com> (raw)
In-Reply-To: <CANn89iJfphTDBFKdNkgmBHDybc8wV2EGSJoiHvzR0ht4V2bMAA@mail.gmail.com>



On 2026/9/15 04:21, Eric Dumazet wrote:
> On Mon, Sep 14, 2026 at 12:57 PM Eric Dumazet <edumazet@google.com> wrote:
>>
>> On Mon, Sep 14, 2026 at 12:51 PM Kuniyuki Iwashima <kuniyu@google.com> wrote:
>>>
>>> On Fri, Sep 11, 2026 at 12:38 AM Linkui Xiao <xiaolinkui@126.com> wrote:
>>>>
>>>> From: Linkui Xiao <xiaolinkui@kylinos.cn>
>>>>
>>>> fib_select_multipath() compares nexthop_nh->nh_saddr against the flow
>>>> source address with no lock held, while fib_info_update_nhc_saddr()
>>>> stores a new value from another CPU as soon as the preferred source
>>>> address of the egress device changes.
>>>>
>>>> Commit 195374d89368 ("ipv4: fib: annotate races around nh->nh_saddr_genid
>>>> and nh->nh_saddr") added WRITE_ONCE() on the store side and READ_ONCE()
>>>> in fib_result_prefsrc() after syzbot reported
>>>>
>>>>          BUG: KCSAN: data-race in fib_select_path / fib_select_path
>>>>
>>>> but it only covered that reader. fib_select_multipath(), reached from
>>>> fib_select_path(), is a second lockless reader of nh->nh_saddr and was
>>>> left bare.
>>>
>>> 32607a332cfe added the reader after 195374d89368.
>>>
>>
>> Indeed, please put in V2:
>>
>> Fixes: 32607a332cfe ("ipv4: prefer multipath nexthop that matches
>> source address")
> 
> Adding Willem
> 
> It seems that this code also lacks a check against genid?
Thanks Eric and Kuniyuki for the correction. I'll send a V2 with Fixes: 
32607a332cfe.

Kuniyuki, good catch on the missing genid check. nh_saddr is only 
meaningful when nh_saddr_genid matches dev_addr_genid, and 
fib_select_multipath() currently skips that validation. I'll fold the 
genid check into V2 along with the READ_ONCE annotations, unless you'd 
prefer to send it as a separate patch. Let me know.

Best regards,
Linkui Xiao
> 
> diff --git a/net/ipv4/fib_semantics.c b/net/ipv4/fib_semantics.c
> index 50e96f86ca59ab164f764f5d2185d158c14a4a6a..5a8bbcb65daaada1c3ae96339cabc2e801653dac
> 100644
> --- a/net/ipv4/fib_semantics.c
> +++ b/net/ipv4/fib_semantics.c
> @@ -2185,6 +2185,7 @@ void fib_select_multipath(struct fib_result
> *res, int hash,
>          bool use_neigh;
>          int score = -1;
>          __be32 saddr;
> +       int genid;
> 
>          if (unlikely(res->fi->nh)) {
>                  nexthop_path_fib_result(res, hash);
> @@ -2193,6 +2194,7 @@ void fib_select_multipath(struct fib_result
> *res, int hash,
> 
>          use_neigh = READ_ONCE(net->ipv4.sysctl_fib_multipath_use_neigh);
>          saddr = fl4 ? fl4->saddr : 0;
> +       genid = saddr ? atomic_read(&net->ipv4.dev_addr_genid) : 0;
> 
>          change_nexthops(fi) {
>                  int nh_upper_bound, nh_score = 0;
> @@ -2205,7 +2207,9 @@ void fib_select_multipath(struct fib_result
> *res, int hash,
>                      (use_neigh && !fib_good_nh(nexthop_nh)))
>                          continue;
> 
> -               if (saddr && nexthop_nh->nh_saddr == saddr)
> +               if (saddr &&
> +                   READ_ONCE(nexthop_nh->nh_saddr_genid) == genid &&
> +                   READ_ONCE(nexthop_nh->nh_saddr) == saddr)
>                          nh_score += 2;
>                  if (hash <= nh_upper_bound)
>                          nh_score++;


  reply	other threads:[~2026-09-15  2:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11  7:37 Linkui Xiao
2026-09-14 19:50 ` Kuniyuki Iwashima
2026-09-14 19:57   ` Eric Dumazet
2026-09-14 20:21     ` Eric Dumazet
2026-09-15  2:36       ` Linkui Xiao [this message]
2026-09-15  3:23         ` Eric Dumazet

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=182acfbd-d03a-4847-8fb8-4d0d29f22107@126.com \
    --to=xiaolinkui@126.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemb@google.com \
    --cc=xiaolinkui@kylinos.cn \
    /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®