netdev - [PATCH 0/7]: Gradual conversion to sk

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: <20080922.191230.127783294.davem@davemloft.net>
Date:	Mon, 22 Sep 2008 19:12:30 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	netdev@...r.kernel.org
Subject: [PATCH 0/7]: Gradual conversion to sk_buff list-head..

As I mentioned in my INFO patch the other day I'm trying to convert
sk_buff to use list_head's.

To make the transition smoother I've started to hit places one by one
that directly reference the sk_buff_head list handling implementation
details and make them use only the provided interfaces.  I've added
new interfaces where necessary to add more parity with what
linux/list.h provides.

Of note is that there are now list splice interfaces, as well as a
"light weight" sk_buff_head initializer for on-stack local list
cases.

There is more to do, but once it's all handled it should be a matter
of only editing linux/skbuff.h and net/core/skbuff.c to perform the
final conversion.

The trickiest part so far is the PPP MP fragmentation reassembly code.
I converted ISDN's copy, and am working on ppp_generic.c's at the moment
in my local tree.

Really we shouldn't have two copies (their implementations are even
slightly different wrt. handling unfinished frames and sequence gaps).

But such consolidation is a task for later.

All of this is pushed to net-next-2.6, so if you encounter some errors
let me know and I'll get them fixed up as fast as possible.
--
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