netdev - Re: SKB paged fragment lifecycle on receive

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: <20110624.124624.1329947216240823992.davem@davemloft.net>
Date:	Fri, 24 Jun 2011 12:46:24 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jeremy@...p.org
Cc:	eric.dumazet@...il.com, Ian.Campbell@...rix.com,
	netdev@...r.kernel.org, xen-devel@...ts.xensource.com,
	rusty@...tcorp.com.au
Subject: Re: SKB paged fragment lifecycle on receive

From: Jeremy Fitzhardinge <jeremy@...p.org>
Date: Fri, 24 Jun 2011 11:21:15 -0700

>> Dangerous I would say. You could have a skb1 page transferred to another
>> skb2, and call skb1 destructor way before page being released.
> 
> Under what circumstances would that happen?

Pages get transferred between different SKBs all the time.

For example, GRO makes extensive use of this technique.
See net/core/skbuff.c:skb_gro_receive().

It is just one example.
--
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