netdev - [PATCH 0/2] ipv4: Fix dangling netdev refs

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

Message-Id: <20120730.182325.572061220480380949.davem@davemloft.net>
Date:	Mon, 30 Jul 2012 18:23:25 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	eric.dumazet@...il.com
CC:	netdev@...r.kernel.org
Subject: [PATCH 0/2] ipv4: Fix dangling netdev refs

Eric, this should give you an idea of what I was working on.

It really assumes the universe in place before your change last
night.  It is very likely we'll have to revert it and look for
another solution to the problem you were trying to solve.  And
actually I don't understand the actual bug very well.

I can only assume that the core issue was that, unlike back when
we had the routing cache, the fib_info nexthops are not persistent
memory like the routing cache hash table was?

Otherwise I can see absolutely no change in reference counting and
dst destruction logic between the routing cache, and how I modified
fib_info nexthop cached routes to behave.

Anyways, the first patch caches routes in the nexthop exception
entries.

And the second patch has a global list for uncached routes so we
can purge netdevice references properly when such devices are
unregistered.

Signed-off-by: David S. Miller <davem@...emloft.net>
--
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