netdev - Re: tbl->lock not taken in neigh

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: <20160124.212045.993259665260998708.davem@davemloft.net>
Date:	Sun, 24 Jan 2016 21:20:45 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	ani@...sta.com
Cc:	netdev@...r.kernel.org, ebiederm@...ssion.com,
	eric.dumazet@...il.com
Subject: Re: tbl->lock not taken in neigh_lookup() ?

From: Ani Sinha <ani@...sta.com>
Date: Mon, 25 Jan 2016 10:11:15 +0530

> Can I get some insights into this? I am sure I am missing something.

The whole point of RCU locking is that read accesses in the fast paths
(lookups) do not need to take the spinlock.  Proper RCU barriers, RCU
deferred freeing of objects, and other things make it safe.