[lkml]   [2022]   [Aug]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] net: Fix suspicious RCU usage in bpf_sk_reuseport_detach()
On Tue, Aug 16, 2022 at 02:09:46PM +0100, David Howells wrote:
> Hawkins Jiawei <> wrote:
> > if (socks) {
> > WRITE_ONCE(sk->sk_user_data, NULL);
> Btw, shouldn't this be rcu_assign_pointer() or RCU_INIT_POINTER(), not
It is not necessary. The sk_user_data usage in reuseport_array
is protected by the sk_callback_lock alone. The code
before the commit cf8c1e967224 is fine. If the
__rcu_dereference_sk_user_data_with_flags() could be reused here as is,
an extra rcu_dereference is fine, so I did not mention it.
It seems it is not the case and new function naming is getting long,
so how about reverting the commit cf8c1e967224 and keep it as it was.

 \ /
  Last update: 2022-08-16 23:50    [W:0.117 / U:1.000 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site