netdev - Re: [PATCH net-2.6] bonding: Bonding driver does not consider the gso_max

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: <1353509087.2590.32.camel@edumazet-glaptop>
Date:	Wed, 21 Nov 2012 06:44:47 -0800
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Neil Horman <nhorman@...driver.com>
Cc:	sarveshwar.bandi@...lex.com, davem@...emloft.net,
	netdev@...r.kernel.org
Subject: Re: [PATCH net-2.6] bonding: Bonding driver does not consider the
 gso_max_size setting of slaves.

On Wed, 2012-11-21 at 06:56 -0500, Neil Horman wrote:

> This seems a bit overly complex.  It doesn't seem like you need the
> reset_go_size bool in here at all.  Just initalize gso_max_size to GSO_MAX_SIZE
> and reduce it every time you find a smaller gso value on a slave.  Then you can
> unilaterally set the bond devices gso_max_size without having to check any bools
> or do any comparisons.

Oh well, I should have read your answer ;)


--
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