linux-kernel - Re: [stable] [PATCH 00/12] xen/paravirt

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:	Wed, 14 Nov 2007 11:03:35 -0800
From:	Greg KH <greg@...ah.com>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	xen-devel@...ts.xensource.com, LKML <linux-kernel@...r.kernel.org>,
	Andi Kleen <ak@...e.de>, Chris Wright <chrisw@...s-sol.org>,
	virtualization@...ts.osdl.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Keir Fraser <keir@...source.com>,
	Stable Kernel <stable@...nel.org>
Subject: Re: [stable] [PATCH 00/12] xen/paravirt_ops patches for 2.6.24

On Wed, Nov 14, 2007 at 10:40:50AM -0800, Jeremy Fitzhardinge wrote:
> Greg KH wrote:
> > These don't apply now due to the x86 merge.  Care to backport them and
> > send them to the stable@...nel.org address so we can apply them
> > properly?
> 
> I'm a bit confused.  The patches you mailed out are against arch/i386. 
> Won't they apply to the stable tree as-is?

Was this second series a new set, or a different one?  I was assuming
they were new patches, and that they too needed to be applied.

These patches were sent against the merged x86 tree, not the -stable
tree with i386.

> > Although, it's not like anyone actually uses the in-kernel Xen on
> > 2.6.23, so it's probably not really worth it.
> >   
> 
> To be fair, those fixes were in response to bug reports raised on the
> released 2.6.23 kernel.  But it isn't screamingly urgent.

Ok, that's fine, but can you send some patches that I can apply?  :)

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/