netdev - [PATCH 0/6]: Get rid of BUS_ID

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

Message-Id: <20090526.213942.196879926.davem@davemloft.net>
Date:	Tue, 26 May 2009 21:39:42 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	netdev@...r.kernel.org
CC:	kay.sievers@...y.org, greg@...ah.com
Subject: [PATCH 0/6]: Get rid of BUS_ID_SIZE in networking

The generic device layer got rid of it's bus name string length
limitations by moving to dynamically allocated strings for names.

But there are things all over the tree that indirectly reference the
old BUS_ID_SIZE.

I had this glorious and ambitious patch almost finished that tried to
tackle the MII_BUS_ID_SIZE thing by similarly implementing dynamic
string lengths there but I gave up. :-) It's a lot of work and I do
not have the hardware to test this, and in order to just simply build
all the effected drivers I would have to use 3 or 4 different cross
compiles.  No thanks.

So most of this is in the form of either "get rid of it", "replace
with constant '20'", or "use MII_BUS_ID instead".

I'm pretty sure I got everything in the networking in net-next-2.6,
so if I missed anything let me know.

(Kay, I'll kill the sparc one in my sparc-next-2.6 tree when I
 next get the chance.)
--
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