netdev - Re: [PATCH] ixgbe: fix for 82599 erratum on Header Splitting

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] [day] [month] [year] [list]

Message-ID: <1299312365.26413.35.camel@jtkirshe-MOBL1>
Date:	Sat, 05 Mar 2011 00:06:05 -0800
From:	Jeff Kirsher <jeffrey.t.kirsher@...el.com>
To:	Greg KH <gregkh@...e.de>
Cc:	"Skidmore, Donald C" <donald.c.skidmore@...el.com>,
	"stable@...nel.org" <stable@...nel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH] ixgbe: fix for 82599 erratum on Header Splitting

On Fri, 2011-03-04 at 23:59 -0800, Greg KH wrote:
> On Fri, Mar 04, 2011 at 11:51:07PM -0800, Jeff Kirsher wrote:
> > On Fri, 2011-03-04 at 23:44 -0800, Greg KH wrote:
> > > On Fri, Mar 04, 2011 at 11:06:07PM -0800, Jeff Kirsher wrote:
> > > > From: Don Skidmore <donald.c.skidmore@...el.com>
> > > > 
> > > > We have found a hardware erratum on 82599 hardware that can lead to
> > > > unpredictable behavior when Header Splitting mode is enabled.  So
> > > > we are no longer enabling this feature on affected hardware.
> > > > 
> > > > Signed-off-by: Don Skidmore <donald.c.skidmore@...el.com>
> > > > Tested-by: Stephen Ko <stephen.s.ko@...el.com>
> > > > Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
> > > > ---
> > > >  drivers/net/ixgbe/ixgbe_main.c |    4 ++++
> > > 
> > > I'm confused, why did you just send this patch to me?
> > > 
> > > What am I supposed to do with it?
> > > 
> > > greg k-h
> > 
> > This is the fix for ixgbe (that Ben and others pointed out) which has
> > been accepted into Linus's tree which did not apply to stable-2.6.32
> > tree.  This is the updated patch that apply's to the stable-2.6.32 tree.
> 
> How nice, but why didn't you say so in the first place?  Am I really
> supposed to remember the hundreds of stable patches I handle every week?

Sorry, I sent you/stable an email saying that I would send you an
updated patch that would apply to stable-2.6.32.  I know you deal with a
number of patches, so I apologize.

> 
> Oh, I need the git commit id of it as well, care to resend this with
> that and the proper "please apply this for the .32 longterm tree"
> message so I can?
> 

Heres is the commit info:
commit a124339ad28389093ed15eca990d39c51c5736cc
Author: Don Skidmore <donald.c.skidmore@...el.com>
Date:   Tue Jan 18 22:53:47 2011 +0000


> If so, I'll queue it up for the after-next .32-longterm release.
> 

I can resend the entire patch submission again, with the info provided,
if necessary.

> thanks,
> 
> greg k-h



Download attachment "signature.asc" of type "application/pgp-signature" (491 bytes)