From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: [PATCH net-next] gro: Handle inline VLAN tags Date: Fri, 16 Nov 2012 16:16:54 -0800 Message-ID: <1353111414.10798.64.camel@edumazet-glaptop> References: <1353097030.2743.28.camel@bwh-desktop.uk.solarflarecom.com> <1353106865.10798.61.camel@edumazet-glaptop> <1353110430.2743.73.camel@bwh-desktop.uk.solarflarecom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: David Miller , netdev@vger.kernel.org, linux-net-drivers@solarflare.com, Andrew Gallatin , Herbert Xu To: Ben Hutchings Return-path: Received: from mail-pa0-f46.google.com ([209.85.220.46]:54667 "EHLO mail-pa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753839Ab2KQAQ5 (ORCPT ); Fri, 16 Nov 2012 19:16:57 -0500 Received: by mail-pa0-f46.google.com with SMTP id hz1so2194602pad.19 for ; Fri, 16 Nov 2012 16:16:56 -0800 (PST) In-Reply-To: <1353110430.2743.73.camel@bwh-desktop.uk.solarflarecom.com> Sender: netdev-owner@vger.kernel.org List-ID: On Sat, 2012-11-17 at 00:00 +0000, Ben Hutchings wrote: > I'm not sure what you mean by this. Is your point that the > copy-on-write is never needed? It is still possible for pskb_may_pull() > to fail. > A packet sniffer should have a copy of bad frames, even if dropped later in our stacks. GRO layer is not allowed to drop a frame, even if not 'correct'.