linux-kernel - Re: [PATCH 2.6.20.4] Flush MSI-X table writes (rev 3)

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: <20070330194854.GA7857@suse.de>
Date:	Fri, 30 Mar 2007 12:48:54 -0700
From:	Greg KH <gregkh@...e.de>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	Mitch Williams <mitch.a.williams@...el.com>,
	linux-pci@...ey.karlin.mff.cuni.cz, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, auke-jan.h.kok@...el.com
Subject: Re: [PATCH 2.6.20.4] Flush MSI-X table writes (rev 3)

On Fri, Mar 30, 2007 at 01:33:45PM -0600, Eric W. Biederman wrote:
> Greg KH <gregkh@...e.de> writes:
> >
> > Sorry, but this isn't going to go into 2.6.20 any time soon as it
> > doesn't fit the rules for the -stable tree.
> >
> > But I'll take an updated version for my pci tree to go to Linus after
> > 2.6.21 is out.
> 
> Greg this does fix a bug that affects 2.6.21.  We have hardware in 2.6.21 that
> is affected And it at least seems to meet the obviously correct
> criteria.  So at least for 2.6.21 I think it is interesting.

We do?  What hardware has this reported problem showed up on?  I haven't
seen any bug reports yet.

And I think it's way too late for something like this.  If it's really
needed, I don't have a problem adding it to the 2.6.21-stable tree in a
few weeks.

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/