From: Yue Haibing <yuehaibing@huawei.com>
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: <davem@davemloft.net>, <dsahern@kernel.org>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<horms@kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] ipv6: annotate data-races around devconf->rpl_seg_enabled
Date: Tue, 26 Aug 2025 21:32:34 +0800 [thread overview]
Message-ID: <ab973374-88cd-4b06-986f-56393b32ce06@huawei.com> (raw)
In-Reply-To: <CAAVpQUDA5gCi--n9N7PQZC3rDBxhZxMW8AUFoaGs+09oT6Vebg@mail.gmail.com>
On 2025/8/26 11:17, Kuniyuki Iwashima wrote:
> On Mon, Aug 25, 2025 at 7:51 PM Yue Haibing <yuehaibing@huawei.com> wrote:
>>
>> devconf->rpl_seg_enabled can be changed concurrently from
>> /proc/sys/net/ipv6/conf, annotate lockless reads on it.
>>
>> Signed-off-by: Yue Haibing <yuehaibing@huawei.com>
>> ---
>> net/ipv6/exthdrs.c | 6 ++----
>> 1 file changed, 2 insertions(+), 4 deletions(-)
>>
>> diff --git a/net/ipv6/exthdrs.c b/net/ipv6/exthdrs.c
>> index d1ef9644f826..a23eb8734e15 100644
>> --- a/net/ipv6/exthdrs.c
>> +++ b/net/ipv6/exthdrs.c
>> @@ -494,10 +494,8 @@ static int ipv6_rpl_srh_rcv(struct sk_buff *skb)
>>
>> idev = __in6_dev_get(skb->dev);
>>
>> - accept_rpl_seg = net->ipv6.devconf_all->rpl_seg_enabled;
>> - if (accept_rpl_seg > idev->cnf.rpl_seg_enabled)
>> - accept_rpl_seg = idev->cnf.rpl_seg_enabled;
>> -
>> + accept_rpl_seg = min(READ_ONCE(net->ipv6.devconf_all->rpl_seg_enabled),
>> + READ_ONCE(idev->cnf.rpl_seg_enabled));
>> if (!accept_rpl_seg) {
>
> Orthogonal to this change, but rpl_seg_enabled is missing .extra1/2
> or this condition should be adjusted like other knobs that recognises
> <0 as disabled, .e.g. keep_addr_on_down, etc.
Thanks, will add .extra1/2 check for this in v2.
>
>
>> kfree_skb(skb);
>> return -1;
>> --
>> 2.34.1
>>
>
prev parent reply other threads:[~2025-08-26 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 2:52 Yue Haibing
2025-08-26 3:17 ` Kuniyuki Iwashima
2025-08-26 13:32 ` Yue Haibing [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=ab973374-88cd-4b06-986f-56393b32ce06@huawei.com \
--to=yuehaibing@huawei.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®