netdev - [PATCH 0/2] Get rid of "multi-hh

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]

Date:	Wed, 13 Jul 2011 01:52:10 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	netdev@...r.kernel.org
Subject: [PATCH 0/2] Get rid of "multi-hh_cache" capability.

We support having multiple hh_cache entries in a list hung off
of a neighbour entry, one per unique ->hh_type protocol value.

Problem is, nobody uses this.

Neighbour entries are for one protocol type only (which determines the
type of the key), whose protocol is "dst_ops->protocol".

Kill all of this noise, which dates back to before Alexey Kuznetsov
added the neighbour layer.  He just blinded copied over this
capability into the generic layer.

The next step will be to embed "struct hh_cache" directly into "struct
neighbour".  Validity will be indicated by a non-zero hh_len.

Then we can get rid of all of this extra memory allocations, funky
refcounting, and SMP memory barriers.

And finally, move to refcount-less neigh entry usage in ip_finish_output2()
--
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