linux-kernel - Re: [PATCH 2.6.21-rc5] 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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 30 Mar 2007 13:00:22 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Greg KH <gregkh@...e.de>
Cc:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Mitch Williams <mitch.a.williams@...el.com>,
	linux-pci@...ey.karlin.mff.cuni.cz, linux-kernel@...r.kernel.org,
	auke-jan.h.kok@...el.com
Subject: Re: [PATCH 2.6.21-rc5] Flush MSI-X table writes (rev 3)

On Fri, 30 Mar 2007 12:49:56 -0700
Greg KH <gregkh@...e.de> wrote:

> > > Acked-by: "Eric W. Biederman" <ebiederm@...ssion.com>
> > 
> > Did we end up deciding whether this is (needed*safe) enough for 2.6.21?
> 
> I say no for now, I have seen no bug reports for any hardware that is
> not in a lab for this.

Well.  Presumably that hardware will be in the field during the lifetime of
2.6.21-based kernels.

Perhaps we should put this into 2.6.22 then backport it to 2.6.21.x once it
seems safe to do so.  If we decide to go this way, we'll need to ask Mitch
to remind us to do the backport at the appropriate time, else we'll surely
forget.

-
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/