netdev - Re: [PATCH 1/4] bonding: fix device name allocation error

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

Message-ID: <45B5A1DE.4030906@pobox.com>
Date:	Tue, 23 Jan 2007 00:49:18 -0500
From:	Jeff Garzik <jgarzik@...ox.com>
To:	Jay Vosburgh <fubar@...ibm.com>
CC:	netdev@...r.kernel.org, bonding-devel@...ts.sourceforge.net,
	Patrick McHardy <kaber@...sh.net>, mitch.a.williams@...el.com
Subject: Re: [PATCH 1/4] bonding: fix device name allocation error

Jay Vosburgh wrote:
> 	The code to select names for the bonding interfaces was, for the
> non-sysfs creation case, always using a hard-coded set of bond0, bond1,
> etc, up to max_bonds.  This caused conflicts for the second or
> subsequent loads of the module.
> 
> 	Changed the code to obtain device names from dev_alloc_name().
> 
> Signed-off-by: Jay Vosburgh <fubar@...ibm.com>

applied 1-4 to #upstream


-
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