From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: OVMF/Xen, Debian wheezy can't boot with NX on stack (Was: Re: [edk2] [PATCH] OvmfPkg: prevent code execution from DXE stack) Date: Mon, 14 Sep 2015 13:23:43 +0100 Message-ID: <1442233423.3549.192.camel@citrix.com> References: <1438963209-5241-1-git-send-email-lersek@redhat.com> <0C09AFA07DD0434D9E2A0C6AEB0483100217660B@shsmsx102.ccr.corp.intel.com> <55E01918.1090406@redhat.com> <20150908172615.GA1529@perard.uk.xensource.com> <55EF5FEE.7010701@redhat.com> <55EFF6A202000078000A116F@prv-mh.provo.novell.com> <1441791460.24450.232.camel@citrix.com> <55F00E94.5040503@redhat.com> <55F2BE79.4010008@redhat.com> <20150911141035.GA6644@x> <55F2F306.2090104@redhat.com> <1442222558.3549.113.camel@citrix.com> <55F6AA56.4030105@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <55F6AA56.4030105@redhat.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Laszlo Ersek , Josh Triplett Cc: Jordan L Justen , edk2-devel-01 , Xen Devel , "Gabriel L. Somlo (GMail)" , Gary Ching-Pang Lin , Jan Beulich , Anthony PERARD , Paolo Bonzini , Star Zeng List-Id: xen-devel@lists.xenproject.org On Mon, 2015-09-14 at 13:07 +0200, Laszlo Ersek wrote: > Debian Wheezy is not very old, it's only a year older than RHEL7 (May > > 2013 > > vs June 2014) and only a bit older than two years in absolute terms. It is > > also the subject of an LTS effort, which extends its lifetime to 2018. > > (*) > > > For comparison Windows 7 (which you argue regressing would be serious) was > > released in 2009 and there have been two major Windows releases since then. > > (**) > > > Given that and with consideration between the desire to run older platforms > > vs. a development environment it seems to me that Debian Wheezy has not yet > > reached the threshold for being ignored or for saying to users "you must > > now upgrade". > > I believe I could argue against both (*) and (**), but it would not be > productive. :) Yes, I'm sure we could be here until the cows come home to roost ;-) > Instead, what matters is the (now) clear, significant user demand for > turning off PcdSetNxForStack by default. I'll send a followup patch for > my series to that end. Thanks. > And, sorry about the inconvenience the regression may have caused, of > course ;) No need to apologise, it was an experiment worth performing IMHO. Ian.