From: Ian Campbell <ian.campbell@citrix.com>
To: Laszlo Ersek <lersek@redhat.com>, Josh Triplett <josh@joshtriplett.org>
Cc: Jordan L Justen <jordan.l.justen@intel.com>,
edk2-devel-01 <edk2-devel@ml01.01.org>,
Xen Devel <xen-devel@lists.xen.org>,
"Gabriel L. Somlo (GMail)" <gsomlo@gmail.com>,
Gary Ching-Pang Lin <glin@suse.com>,
Jan Beulich <JBeulich@suse.com>,
Anthony PERARD <anthony.perard@citrix.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Star Zeng <star.zeng@intel.com>
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 [thread overview]
Message-ID: <1442233423.3549.192.camel@citrix.com> (raw)
In-Reply-To: <55F6AA56.4030105@redhat.com>
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.
prev parent reply other threads:[~2015-09-14 12:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1438963209-5241-1-git-send-email-lersek@redhat.com>
[not found] ` <0C09AFA07DD0434D9E2A0C6AEB0483100217660B@shsmsx102.ccr.corp.intel.com>
[not found] ` <55E01918.1090406@redhat.com>
2015-09-08 17:26 ` OVMF/Xen, Debian wheezy can't boot with NX on stack (Was: Re: [edk2] [PATCH] OvmfPkg: prevent code execution from DXE stack) Anthony PERARD
[not found] ` <20150908172615.GA1529@perard.uk.xensource.com>
2015-09-08 22:23 ` Laszlo Ersek
[not found] ` <55EF5FEE.7010701@redhat.com>
2015-09-09 7:06 ` Jan Beulich
2015-09-09 9:24 ` Laszlo Ersek
2015-09-09 9:37 ` Ian Campbell
2015-09-09 10:06 ` Jan Beulich
2015-09-09 10:48 ` Laszlo Ersek
[not found] ` <55F00E94.5040503@redhat.com>
2015-09-09 11:07 ` Ian Campbell
2015-09-09 11:30 ` Paolo Bonzini
2015-09-09 11:30 ` Laszlo Ersek
[not found] ` <55F0186E.3020001@redhat.com>
2015-09-09 11:41 ` Laszlo Ersek
[not found] ` <55F01873.5000505@redhat.com>
2015-09-10 3:21 ` [edk2] OVMF/Xen, Debian wheezy can't boot with NX on stack (Was: " Zeng, Star
2015-09-09 12:08 ` OVMF/Xen, Debian wheezy can't boot with NX on stack (Was: Re: [edk2] " Jan Beulich
2015-09-09 13:04 ` Laszlo Ersek
[not found] ` <55F02E58.3090504@redhat.com>
2015-09-09 13:10 ` Jan Beulich
2015-09-10 3:05 ` Zeng, Star
[not found] ` <55F0F35F.7060702@intel.com>
2015-09-10 9:38 ` Laszlo Ersek
2015-09-11 11:43 ` Laszlo Ersek
[not found] ` <55F2BE79.4010008@redhat.com>
2015-09-11 14:10 ` Josh Triplett
[not found] ` <20150911141035.GA6644@x>
2015-09-11 15:28 ` Laszlo Ersek
[not found] ` <55F2F306.2090104@redhat.com>
2015-09-11 19:30 ` Josh Triplett
[not found] ` <20150911193028.GB10395@x>
2015-09-11 21:27 ` Laszlo Ersek
[not found] ` <55F34744.2050308@redhat.com>
2015-09-11 23:06 ` Josh Triplett
[not found] ` <20150911230639.GA19127@x>
2015-09-14 10:57 ` Laszlo Ersek
2015-09-14 9:22 ` Ian Campbell
2015-09-14 11:07 ` Laszlo Ersek
[not found] ` <55F6AA56.4030105@redhat.com>
2015-09-14 12:23 ` Ian Campbell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1442233423.3549.192.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=anthony.perard@citrix.com \
--cc=edk2-devel@ml01.01.org \
--cc=glin@suse.com \
--cc=gsomlo@gmail.com \
--cc=jordan.l.justen@intel.com \
--cc=josh@joshtriplett.org \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.com \
--cc=star.zeng@intel.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.