netdev - Re: [PATCH net] sctp: Hold RCU read lock while iterating over address list

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <cf5df107-1056-48b1-aec5-f70043a9c31c@nokia.com>
Date: Fri, 24 Oct 2025 10:50:56 +0200
From: Stefan Wiehler <stefan.wiehler@...ia.com>
To: Kuniyuki Iwashima <kuniyu@...gle.com>, Xin Long <lucien.xin@...il.com>
Cc: davem@...emloft.net, edumazet@...gle.com, horms@...nel.org,
 kuba@...nel.org, linux-kernel@...r.kernel.org, linux-sctp@...r.kernel.org,
 netdev@...r.kernel.org, pabeni@...hat.com
Subject: Re: [PATCH net] sctp: Hold RCU read lock while iterating over address
 list

> Or if lock_sock() is enough, we should use the plain
> list_for_each_entry(), or list_for_each_entry_rcu() with
> lockdep_sock_is_held() as the 4th arg.

Right, I've already hinted in the commit comment that lock_sock() might be
enough, but I'm not sure about it...

@Xin Long, as you're the author and have already acked, I suppose we actually
need to hold the RCU read lock?