Re: [PATCH net] bonding: avoid defaulting hard_header_len to ETH_HLEN on slave removal

2017-04-28 Thread David Miller
From: Paolo Abeni Date: Thu, 27 Apr 2017 19:29:34 +0200 > On slave list updates, the bonding driver computes its hard_header_len > as the maximum of all enslaved devices's hard_header_len. > If the slave list is empty, e.g. on last enslaved device removal, > ETH_HLEN is used. > > Since the bondi

Re: [PATCH net] bonding: avoid defaulting hard_header_len to ETH_HLEN on slave removal

2017-04-27 Thread Jay Vosburgh
Paolo Abeni wrote: >On slave list updates, the bonding driver computes its hard_header_len >as the maximum of all enslaved devices's hard_header_len. >If the slave list is empty, e.g. on last enslaved device removal, >ETH_HLEN is used. > >Since the bonding header_ops are set only when the first e

Re: [PATCH net] bonding: avoid defaulting hard_header_len to ETH_HLEN on slave removal

2017-04-27 Thread Marcelo Ricardo Leitner
On Thu, Apr 27, 2017 at 07:29:34PM +0200, Paolo Abeni wrote: > On slave list updates, the bonding driver computes its hard_header_len > as the maximum of all enslaved devices's hard_header_len. > If the slave list is empty, e.g. on last enslaved device removal, > ETH_HLEN is used. > > Since the bo

[PATCH net] bonding: avoid defaulting hard_header_len to ETH_HLEN on slave removal

2017-04-27 Thread Paolo Abeni
On slave list updates, the bonding driver computes its hard_header_len as the maximum of all enslaved devices's hard_header_len. If the slave list is empty, e.g. on last enslaved device removal, ETH_HLEN is used. Since the bonding header_ops are set only when the first enslaved device is attached,