netdev - Re: [PATCH]: net/bonding: Enable to change device type before enslaving

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

Message-ID: <21771.1207860504@death>
Date:	Thu, 10 Apr 2008 13:48:24 -0700
From:	Jay Vosburgh <fubar@...ibm.com>
To:	monis@...taire.com
cc:	netdev <netdev@...r.kernel.org>, Olga Stern <olgas@...taire.com>,
	Or Gerlitz <ogerlitz@...taire.com>
Subject: Re: [PATCH]: net/bonding: Enable to change device type before enslaving 

Moni Shoua <monis@...taire.com> wrote:

>
>The bonding network device is being created  with device type ARPHDR_ETHER.
>Although the device type changes with first slave we want to be able to change
>it when it has zero slaves. The reason is to make the kernel choose the right
>function for multicast address translation (ib_xxx_mc_map) which is determined by
>device type even when no slaves are enslaved. If not so, the kernel picks a wrong
>translation function and wrong HW addresses will be passed to slaves when the
>bonding device tries to set their multicast lists.

	Does this mean that the automatic selection on first enslavement
is no longer needed, and all setting of the type for IB devices must
occur prior to first enslavement?

	Or is this more of a special case for some devices, and the
automatic selection is still correct for most cases?

	-J

---
	-Jay Vosburgh, IBM Linux Technology Center, fubar@...ibm.com
--
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