stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Duyck, Alexander H" <alexander.h.duyck@intel.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"edumazet@google.com" <edumazet@google.com>
Cc: "maan@tuebingen.mpg.de" <maan@tuebingen.mpg.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"ast@kernel.org" <ast@kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"willemb@google.com" <willemb@google.com>,
	"jslaby@suse.cz" <jslaby@suse.cz>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"yibyang@cisco.com" <yibyang@cisco.com>
Subject: Re: Linux 4.4.34
Date: Tue, 22 Nov 2016 17:41:53 +0000	[thread overview]
Message-ID: <1479836511.681.165.camel@intel.com> (raw)
In-Reply-To: <CANn89iJCkHxOpE3TW8+gW8+UCVvT0mY8y8j_GJC1GK0i05dgbg@mail.gmail.com>

On Tue, 2016-11-22 at 09:14 -0800, Eric Dumazet wrote:
> On Tue, Nov 22, 2016 at 9:06 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > 
> > On Tue, Nov 22, 2016 at 05:59:12PM +0100, Andre Noll wrote:
> > > 
> > > On Mon, Nov 21, 10:28, Greg KH wrote
> > > > 
> > > > I'm announcing the release of the 4.4.34 kernel.
> > > > 
> > > > All users of the 4.4 kernel series must upgrade.
> > > 
> > > This update broke PXE boot on our 4-way AMD boxes. The kernel panics in
> > > eth_type_trans(), presumably during kernel-level IP autoconfiguration,
> > > see [1]. Bisection points me at 5c67f947 (net: __skb_flow_dissect()
> > > must cap its return value). And indeed, reverting this commit fixes
> > > the problem for me.
> > > 
> > > Investigation showed that the real problem is not the change in the
> > > above commit per se (i.e., capping ->thoff) but the fact that in the
> > > success case, where we jump to the "out_good" label, ->thoff is now
> > > set *after* ->n_proto and ->ip_proto. I fail to see how order matters
> > > here, but it clearly does, since the crash is 100% reproducible,
> > > and is fixed by the commit below (on top of v4.4.34).
> > > 
> > > Please consider applying something like the patch below for mainline
> > > and -stable.
> > 
> > If this issue is also the same for Linus's tree, we should cc: netdev so
> > that the patch can get into there, right?
> > 
> > thanks,
> > 
> > greg k-h
> 
> We definitely want to fix the real bug, not working around it.
> 
> Seems an aliasing problem, key_control and key_basic might point to
> adjacent memory
> and a barrier() would solve the issue as well.
> 
> Adding a test in fast path looks overkill to me.
> 
> Thanks.

I was wondering if we shouldn't just cap all cases?

It seems like this could potentially return a value greater than skb-
>len in the "good" case since things like IP header length isn't
validated other then making sure it meets the minimum value, and if
there isn't a recognized L4 header after that we could return that as a
final value.

- Alex

  parent reply	other threads:[~2016-11-22 17:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-21  9:28 Linux 4.4.34 Greg KH
2016-11-21  9:28 ` Greg KH
2016-11-22 16:59 ` Andre Noll
2016-11-22 17:06   ` Greg KH
2016-11-22 17:14     ` Eric Dumazet
2016-11-22 17:38       ` Andre Noll
2016-11-22 17:41       ` Duyck, Alexander H [this message]
2016-11-22 17:46         ` Eric Dumazet
2016-11-22 17:55           ` Andre Noll
2016-11-22 17:56             ` Eric Dumazet
2016-11-22 18:03               ` Duyck, Alexander H
2016-11-22 18:06               ` Andre Noll
2016-11-22 18:08                 ` Duyck, Alexander H
2016-11-22 18:18                   ` Eric Dumazet
2016-11-22 18:22                   ` Andre Noll
2016-11-22 17:22     ` Andre Noll
2016-11-22 17:26       ` Eric Dumazet
2016-11-22 17:29       ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1479836511.681.165.camel@intel.com \
    --to=alexander.h.duyck@intel.com \
    --cc=ast@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maan@tuebingen.mpg.de \
    --cc=stable@vger.kernel.org \
    --cc=willemb@google.com \
    --cc=yibyang@cisco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).