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]
Date:	Wed, 22 May 2013 04:32:06 -0700
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Pekka Riikonen <priikone@....fi>
Cc:	Simon Horman <horms@...ge.net.au>, dev@...nvswitch.org,
	netdev@...r.kernel.org, Jesse Gross <jesse@...ira.com>,
	Pravin B Shelar <pshelar@...ira.com>,
	jarno.rajahalme@....com,
	Maciej Żenczykowski <maze@...gle.com>
Subject: Re: [PATCH next-next v4 1/2] net: Use 16bits for inner_*_headers
 fields of struct skbuff

On Wed, 2013-05-22 at 09:25 +0200, Pekka Riikonen wrote:
> On Wed, 22 May 2013, Simon Horman wrote:
> 
> > include/linux/skbuff.h | 63 +++++++-------------------------------------------
> > 1 file changed, 8 insertions(+), 55 deletions(-)
> >
> > diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
> > index 2e0ced1..3791615 100644
> > --- a/include/linux/skbuff.h
> > +++ b/include/linux/skbuff.h
> > @@ -509,9 +509,9 @@ struct sk_buff {
> > 		__u32		reserved_tailroom;
> > 	};
> >
> > -	sk_buff_data_t		inner_transport_header;
> > -	sk_buff_data_t		inner_network_header;
> > -	sk_buff_data_t		inner_mac_header;
> > +	__u16			inner_transport_header;
> > +	__u16			inner_network_header;
> > +	__u16			inner_mac_header;
> > 	sk_buff_data_t		transport_header;
> > 	sk_buff_data_t		network_header;
> > 	sk_buff_data_t		mac_header;
> >
> Why not take one more step and use 16-bit fields for the other header 
> fields too: transport_header, network_header and mac_header?

Thats more risky [1], but definitely worth doing

[1] 
commit 50bceae9bd3569d56744882f3012734d48a1d413
Author: Thomas Graf <tgraf@...g.ch>
Date:   Thu Apr 11 10:57:18 2013 +0000

    tcp: Reallocate headroom if it would overflow csum_start
    
    If a TCP retransmission gets partially ACKed and collapsed multiple
    times it is possible for the headroom to grow beyond 64K which will
    overflow the 16bit skb->csum_start which is based on the start of
    the headroom. It has been observed rarely in the wild with IPoIB due
    to the 64K MTU.
    
    Verify if the acking and collapsing resulted in a headroom exceeding
    what csum_start can cover and reallocate the headroom if so.
    
    A big thank you to Jim Foraker <foraker1@...l.gov> and the team at
    LLNL for helping out with the investigation and testing.
    
    Reported-by: Jim Foraker <foraker1@...l.gov>
    Signed-off-by: Thomas Graf <tgraf@...g.ch>
    Acked-by: Eric Dumazet <edumazet@...gle.com>
    Signed-off-by: David S. Miller <davem@...emloft.net>



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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ