netdev - Re: Question about skb

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]

Date:	Sun, 9 Feb 2014 10:42:09 +0800
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	Arnaud Ebalard <arno@...isbad.org>
Cc:	David Miller <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>, Willy Tarreau <w@....eu>,
	netdev@...r.kernel.org
Subject: Re: Question about skb_segment()

On Wed, Jan 29, 2014 at 09:12:57AM +0100, Arnaud Ebalard wrote:
> Hi Herbert,
> 
> I wonder if you could share some knowledge on the behaviour of
> skb_segment() as it is implemented in 3.13.0: when passed a GSO
> packet to be segmented, can the skb result have skb->next == NULL?
> 
> One would expect the number of segments of the result to usually match
> tcp_skb_pcount() of passed packet and hence having skb->next != NULL: 
> AFAICT, this what usually happens when skb_segment() is called in
> tcp_gso_segment() but I noticed some cases where the number of segments
> (length of chained sk_buff) is lower than the expected value and also
> have two backtraces resulting from a skb delivered with a NULL skb->next. 

Hi Arnaud:

This is definitely not expected.  You said that the crash is not
easily reproducible.  Are you able to easily reproduce the problem
where the number of segments produced is less than what is expected?

Can you print out the size of the segments produced in that case?

Thanks!
-- 
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
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