linux-kernel - Re: [PATCH] net: mark racy access on sk->sk

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAL+tcoAHN_-c6eVuOY=O_8xJ_KLPS9yUpeW524nuSMo5RXd3jw@mail.gmail.com>
Date: Sat, 9 Mar 2024 22:49:19 +0800
From: Jason Xing <kerneljasonxing@...il.com>
To: linke li <lilinke99@...com>
Cc: edumazet@...gle.com, alexander@...alicyn.com, davem@...emloft.net, 
	dhowells@...hat.com, kuba@...nel.org, kuniyu@...zon.com, leitao@...ian.org, 
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org, pabeni@...hat.com, 
	willemb@...gle.com, wuyun.abel@...edance.com
Subject: Re: [PATCH] net: mark racy access on sk->sk_rcvbuf

On Sat, Mar 9, 2024 at 10:10 PM linke li <lilinke99@...com> wrote:
>
> > 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.

During that process, I see no lock owning the socket, so sk->sk_rcvbuf
should also be read locklessly.

Thanks,
Jason

>
>