[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5457C807.5080509@linaro.org>
Date: Mon, 03 Nov 2014 18:23:03 +0000
From: Zoltan Kiss <zoltan.kiss@...aro.org>
To: David Vrabel <david.vrabel@...rix.com>,
Ian Campbell <Ian.Campbell@...rix.com>
CC: netdev@...r.kernel.org,
Malcolm Crossley <malcolm.crossley@...rix.com>,
Wei Liu <wei.liu2@...rix.com>, xen-devel@...ts.xenproject.org
Subject: Re: [Xen-devel] [PATCHv1 net-next] xen-netback: remove unconditional
pull_skb_tail in guest Tx path
On 03/11/14 17:46, David Vrabel wrote:
> On 03/11/14 17:39, Ian Campbell wrote:
>> On Mon, 2014-11-03 at 17:23 +0000, David Vrabel wrote:
>>> From: Malcolm Crossley <malcolm.crossley@...rix.com>
>>>
>>> Unconditionally pulling 128 bytes into the linear buffer is not
>>> required. Netback has already grant copied up-to 128 bytes from the
>>> first slot of a packet into the linear buffer. The first slot normally
>>> contain all the IPv4/IPv6 and TCP/UDP headers.
>>
>> What about when it doesn't? It sounds as if we now won't pull up, which
>> would be bad.
>
> The network stack will always pull any headers it needs to inspect (the
> frag may be a userspace page which has the same security issues as a
> frag with a foreign page).
I wouldn't bet my life on this, but indeed it should always happen.
>
> e.g., see skb_checksum_setup() called slightly later on in netback.
Fortunately the call to checksum_setup a bit later makes sure that at
least the TCP/UDP headers are in the linear area, which is quite the
same as blindly pulling 128 bytes. With any other protocol we rely on
the network stack that it will enforce packet header in the linear buffer.
Regards,
Zoli
--
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