| 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
| ||
|
Message-ID: <20080616223508.GA1165@kroah.com> Date: Mon, 16 Jun 2008 15:35:08 -0700 From: Greg KH <greg@...ah.com> To: Jeremy Fitzhardinge <jeremy@...p.org> Cc: the arch/x86 maintainers <x86@...nel.org>, Stable Kernel <stable@...nel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [stable] [PATCH 2/2] xen: don't drop NX bit On Mon, Jun 16, 2008 at 03:01:56PM -0700, Jeremy Fitzhardinge wrote: > When converting the pfn/mfn in a pagetable entry, make sure we mask > out the protection flags properly. Formerly, this code was losing the > NX bit, and not dealing with extra Xen-defined software flags in ptes. > > Because NX is now enforced properly, we must put the hypercall page > into the .text segment so that it is executable. > > Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com> > Cc: Stable Kernel <stable@...nel.org> While it's great that you tell the stable people about this, but is it realistic? Is anyone using Xen as contained in the mainline kernel these days? If a distro were to be based on 2.6.25 and we take this patch, they will just revert it back out due to their very large Xen patchset they apply on top to get a "working" Xen version, right? 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/
Powered by blists - more mailing lists