From: linke li <lilinke99@qq.com>
To: edumazet@google.com
Cc: alexander@mihalicyn.com, davem@davemloft.net,
dhowells@redhat.com, kuba@kernel.org, kuniyu@amazon.com,
leitao@debian.org, lilinke99@qq.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, willemb@google.com, wuyun.abel@bytedance.com
Subject: Re: [PATCH] net: mark racy access on sk->sk_rcvbuf
Date: Sat, 9 Mar 2024 21:59:02 +0800 [thread overview]
Message-ID: <tencent_4E77E34FDA2F438430621DF220620A882407@qq.com> (raw)
In-Reply-To: <CANn89iJRXjYTojFyHN6s1Qu9Vkkk6RwxPF=bAKPjOg9zT-GupA@mail.gmail.com>
> OK, but what about __sock_queue_rcv_skb() in the same file ?
I notice that, but I am not very sure whether there is a data race. If it
is a similar situation, then the same patch should be applied too.
next prev parent reply other threads:[~2024-03-09 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 13:34 [PATCH] net: mark racy access on sk->sk_rcvbuf linke li
2024-03-09 13:50 ` Eric Dumazet
2024-03-09 13:59 ` linke li [this message]
2024-03-09 14:49 ` Jason Xing
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=tencent_4E77E34FDA2F438430621DF220620A882407@qq.com \
--to=lilinke99@qq.com \
--cc=alexander@mihalicyn.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
--cc=wuyun.abel@bytedance.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