netdev - Re: [PATCH] inetpeer: Don't disable BH for initial fast RCU lookup.

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: <20110313.164215.193721466.davem@davemloft.net>
Date:	Sun, 13 Mar 2011 16:42:15 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	eric.dumazet@...il.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH] inetpeer: Don't disable BH for initial fast RCU lookup.

From: Eric Dumazet <eric.dumazet@...il.com>
Date: Sun, 13 Mar 2011 11:04:09 +0100

> David, I am not sure this is safe, since we use call_rcu_bh() when
> freeing one item. One cpu could decide to kfree() one item while another
> cpu could still use it.
> 
> rcu_read_lock_bh() was signalling to others cpu we were in a softirq
> section, so we were delaying a possible kfree().

Ok, could we use normal call_rcu() to solve this then?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html