netdev - Re: [PATCH 10/16] ipv4: Cache output routes in fib

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: <20120719.151312.1882340232448320251.davem@davemloft.net>
Date:	Thu, 19 Jul 2012 15:13:12 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	eric.dumazet@...il.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH 10/16] ipv4: Cache output routes in fib_info nexthops.

From: Eric Dumazet <eric.dumazet@...il.com>
Date: Fri, 20 Jul 2012 00:09:03 +0200

> If we find orig not null, what can protect another cpu from reading
> nh->nh_rth_output, then we dst_release(orig), and other cpu  does the
> dst_use() too late ?

Indeed, we'd have to defer it somehow.

Actually, we might be able to fake this by using __dst_free() on it
or something similar.

But safest would be RCU, whose protection we are still using on the
read side.

Any better ideas?

--
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