From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Benc Subject: Re: [PATCH net-next v2 1/3] openvswitch: normalize vlan rx path Date: Wed, 5 Oct 2016 21:07:09 +0200 Message-ID: <20161005210709.79732b27@griffin> References: <20161005192319.713d92e1@griffin> <20161005184426.GQ25403@egarver> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Eyal Birger , "netdev@vger.kernel.org" , pravin shelar To: Eric Garver Return-path: Received: from mx1.redhat.com ([209.132.183.28]:37168 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752617AbcJETHT (ORCPT ); Wed, 5 Oct 2016 15:07:19 -0400 In-Reply-To: <20161005184426.GQ25403@egarver> Sender: netdev-owner@vger.kernel.org List-ID: On Wed, 5 Oct 2016 14:44:26 -0400, Eric Garver wrote: > On Wed, Oct 05, 2016 at 08:31:52PM +0300, Eyal Birger wrote: > > Just seemed less future safe to keep a pointer to an old packet lying around. > > I agree. Alternatively refresh the eth pointer. Sorry guys, that just doesn't make sense. Everyone should know that reloading of skb pointer means the former pointers to its data may become invalid. Please point me to any place in the kernel where we reload the data pointer "just because" even when not used. Jiri