All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Chris Wright <chrisw@sous-sol.org>
Cc: xen-devel@lists.xensource.com,
	Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>,
	linux-kernel@vger.kernel.org, Mike Travis <travis@sgi.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	virtualization@lists.osdl.org, Yinghai Lu <yhlu.kernel@gmail.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
	Jeremy Fitzhardinge <jeremy@xensource.com>
Subject: Re: 2.6.29 git, resume from ram broken on thinkpad
Date: Fri, 3 Apr 2009 19:39:55 +0200	[thread overview]
Message-ID: <20090403173955.GD6295@elte.hu> (raw)
In-Reply-To: <20090403173631.GA27148@sequoia.sous-sol.org>


* Chris Wright <chrisw@sous-sol.org> wrote:

> * Arkadiusz Miskiewicz (a.miskiewicz@gmail.com) wrote:
> > On Friday 03 of April 2009, Chris Wright wrote:
> > > * Arkadiusz Miskiewicz (a.miskiewicz@gmail.com) wrote:
> > > > What about 9ea09af3bd3090e8349ca2899ca2011bd94cda85 ?
> > > >
> > > > stop_machine: introduce stop_machine_create/destroy.
> > >
> > > That is later fixed in a0e280e0f33f6c859a235fb69a875ed8f3420388.
> > >
> > > Can you please verify if 2.6.29 works for you? 
> > 
> > I think that the guilty part is 
> > CONFIG_CC_STACKPROTECTOR_ALL=y
> > CONFIG_CC_STACKPROTECTOR=y
> 
> Indeed, I think you're right.  In fact...this should fix it:

Note that i had to do a manual merge of the patch (it had 3 separate 
patch corruptions) - the non-damaged version i applied is the one 
below.

	Ingo

--------------->
From 1f23b77e09be10edb30eb03c1b03879083e3cc72 Mon Sep 17 00:00:00 2001
From: Joseph Cihula <joseph.cihula@intel.com>
Date: Mon, 30 Mar 2009 14:03:01 -0700
Subject: [PATCH] x86: disable stack-protector for __restore_processor_state()

The __restore_processor_state() fn restores %gs on resume from S3.  As
such, it cannot be protected by the stack-protector guard since %gs will
not be correct on function entry.

There are only a few other fns in this file and it should not negatively
impact kernel security that they will also have the stack-protector
guard removed (and so it's not worth moving them to another file).

Without this change, S3 resume on a kernel built with
CONFIG_CC_STACKPROTECTOR_ALL=y will fail.

Signed-off-by: Joseph Cihula <joseph.cihula@intel.com>
Cc: Arjan van de Ven <arjan@linux.intel.com>
Cc: Tejun Heo <tj@kernel.org>
LKML-Reference: <49D13385.5060900@intel.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
 arch/x86/power/Makefile |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/arch/x86/power/Makefile b/arch/x86/power/Makefile
index 9ff4d5b..58b32db 100644
--- a/arch/x86/power/Makefile
+++ b/arch/x86/power/Makefile
@@ -1,2 +1,7 @@
+# __restore_processor_state() restores %gs after S3 resume and so should not
+# itself be stack-protected
+nostackp := $(call cc-option, -fno-stack-protector)
+CFLAGS_cpu_$(BITS).o	:= $(nostackp)
+
 obj-$(CONFIG_PM_SLEEP)		+= cpu_$(BITS).o
 obj-$(CONFIG_HIBERNATION)	+= hibernate_$(BITS).o hibernate_asm_$(BITS).o

WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-kernel@vger.kernel.org, Mike Travis <travis@sgi.com>,
	Jeremy Fitzhardinge <jeremy@xensource.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
	virtualization@lists.osdl.org, xen-devel@lists.xensource.com,
	Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: 2.6.29 git, resume from ram broken on thinkpad
Date: Fri, 3 Apr 2009 19:39:55 +0200	[thread overview]
Message-ID: <20090403173955.GD6295@elte.hu> (raw)
In-Reply-To: <20090403173631.GA27148@sequoia.sous-sol.org>


* Chris Wright <chrisw@sous-sol.org> wrote:

> * Arkadiusz Miskiewicz (a.miskiewicz@gmail.com) wrote:
> > On Friday 03 of April 2009, Chris Wright wrote:
> > > * Arkadiusz Miskiewicz (a.miskiewicz@gmail.com) wrote:
> > > > What about 9ea09af3bd3090e8349ca2899ca2011bd94cda85 ?
> > > >
> > > > stop_machine: introduce stop_machine_create/destroy.
> > >
> > > That is later fixed in a0e280e0f33f6c859a235fb69a875ed8f3420388.
> > >
> > > Can you please verify if 2.6.29 works for you? 
> > 
> > I think that the guilty part is 
> > CONFIG_CC_STACKPROTECTOR_ALL=y
> > CONFIG_CC_STACKPROTECTOR=y
> 
> Indeed, I think you're right.  In fact...this should fix it:

Note that i had to do a manual merge of the patch (it had 3 separate 
patch corruptions) - the non-damaged version i applied is the one 
below.

	Ingo

--------------->
>From 1f23b77e09be10edb30eb03c1b03879083e3cc72 Mon Sep 17 00:00:00 2001
From: Joseph Cihula <joseph.cihula@intel.com>
Date: Mon, 30 Mar 2009 14:03:01 -0700
Subject: [PATCH] x86: disable stack-protector for __restore_processor_state()

The __restore_processor_state() fn restores %gs on resume from S3.  As
such, it cannot be protected by the stack-protector guard since %gs will
not be correct on function entry.

There are only a few other fns in this file and it should not negatively
impact kernel security that they will also have the stack-protector
guard removed (and so it's not worth moving them to another file).

Without this change, S3 resume on a kernel built with
CONFIG_CC_STACKPROTECTOR_ALL=y will fail.

Signed-off-by: Joseph Cihula <joseph.cihula@intel.com>
Cc: Arjan van de Ven <arjan@linux.intel.com>
Cc: Tejun Heo <tj@kernel.org>
LKML-Reference: <49D13385.5060900@intel.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
 arch/x86/power/Makefile |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/arch/x86/power/Makefile b/arch/x86/power/Makefile
index 9ff4d5b..58b32db 100644
--- a/arch/x86/power/Makefile
+++ b/arch/x86/power/Makefile
@@ -1,2 +1,7 @@
+# __restore_processor_state() restores %gs after S3 resume and so should not
+# itself be stack-protected
+nostackp := $(call cc-option, -fno-stack-protector)
+CFLAGS_cpu_$(BITS).o	:= $(nostackp)
+
 obj-$(CONFIG_PM_SLEEP)		+= cpu_$(BITS).o
 obj-$(CONFIG_HIBERNATION)	+= hibernate_$(BITS).o hibernate_asm_$(BITS).o

WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Chris Wright <chrisw@sous-sol.org>
Cc: xen-devel@lists.xensource.com,
	Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>,
	linux-kernel@vger.kernel.org, Mike Travis <travis@sgi.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	virtualization@lists.osdl.org, Yinghai Lu <yhlu.kernel@gmail.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
	Jeremy Fitzhardinge <jeremy@xensource.com>
Subject: Re: 2.6.29 git, resume from ram broken on thinkpad
Date: Fri, 3 Apr 2009 19:39:55 +0200	[thread overview]
Message-ID: <20090403173955.GD6295@elte.hu> (raw)
In-Reply-To: <20090403173631.GA27148@sequoia.sous-sol.org>


* Chris Wright <chrisw@sous-sol.org> wrote:

> * Arkadiusz Miskiewicz (a.miskiewicz@gmail.com) wrote:
> > On Friday 03 of April 2009, Chris Wright wrote:
> > > * Arkadiusz Miskiewicz (a.miskiewicz@gmail.com) wrote:
> > > > What about 9ea09af3bd3090e8349ca2899ca2011bd94cda85 ?
> > > >
> > > > stop_machine: introduce stop_machine_create/destroy.
> > >
> > > That is later fixed in a0e280e0f33f6c859a235fb69a875ed8f3420388.
> > >
> > > Can you please verify if 2.6.29 works for you? 
> > 
> > I think that the guilty part is 
> > CONFIG_CC_STACKPROTECTOR_ALL=y
> > CONFIG_CC_STACKPROTECTOR=y
> 
> Indeed, I think you're right.  In fact...this should fix it:

Note that i had to do a manual merge of the patch (it had 3 separate 
patch corruptions) - the non-damaged version i applied is the one 
below.

	Ingo

--------------->
>From 1f23b77e09be10edb30eb03c1b03879083e3cc72 Mon Sep 17 00:00:00 2001
From: Joseph Cihula <joseph.cihula@intel.com>
Date: Mon, 30 Mar 2009 14:03:01 -0700
Subject: [PATCH] x86: disable stack-protector for __restore_processor_state()

The __restore_processor_state() fn restores %gs on resume from S3.  As
such, it cannot be protected by the stack-protector guard since %gs will
not be correct on function entry.

There are only a few other fns in this file and it should not negatively
impact kernel security that they will also have the stack-protector
guard removed (and so it's not worth moving them to another file).

Without this change, S3 resume on a kernel built with
CONFIG_CC_STACKPROTECTOR_ALL=y will fail.

Signed-off-by: Joseph Cihula <joseph.cihula@intel.com>
Cc: Arjan van de Ven <arjan@linux.intel.com>
Cc: Tejun Heo <tj@kernel.org>
LKML-Reference: <49D13385.5060900@intel.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
 arch/x86/power/Makefile |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/arch/x86/power/Makefile b/arch/x86/power/Makefile
index 9ff4d5b..58b32db 100644
--- a/arch/x86/power/Makefile
+++ b/arch/x86/power/Makefile
@@ -1,2 +1,7 @@
+# __restore_processor_state() restores %gs after S3 resume and so should not
+# itself be stack-protected
+nostackp := $(call cc-option, -fno-stack-protector)
+CFLAGS_cpu_$(BITS).o	:= $(nostackp)
+
 obj-$(CONFIG_PM_SLEEP)		+= cpu_$(BITS).o
 obj-$(CONFIG_HIBERNATION)	+= hibernate_$(BITS).o hibernate_asm_$(BITS).o

  reply	other threads:[~2009-04-03 17:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-01  9:55 2.6.29 git, resume from ram broken on thinkpad Arkadiusz Miskiewicz
2009-04-01 21:00 ` Chris Wright
2009-04-01 21:00   ` Chris Wright
2009-04-02 20:12   ` Arkadiusz Miskiewicz
2009-04-01 21:29 ` Rafael J. Wysocki
2009-04-01 21:37   ` Chris Wright
2009-04-01 21:37     ` Chris Wright
2009-04-01 21:49     ` Rafael J. Wysocki
2009-04-01 22:14       ` Chris Wright
2009-04-01 22:23         ` Rafael J. Wysocki
2009-04-01 23:06           ` Chris Wright
2009-04-01 23:06             ` Chris Wright
2009-04-02 21:00             ` Rafael J. Wysocki
2009-04-02 21:04               ` Ingo Molnar
2009-04-02 21:04                 ` Ingo Molnar
2009-04-02 21:28                 ` Rafael J. Wysocki
2009-04-03  0:22                   ` Arkadiusz Miskiewicz
2009-04-03  0:35                     ` Chris Wright
2009-04-03  0:35                       ` Chris Wright
2009-04-03  6:47                       ` Arkadiusz Miskiewicz
2009-04-03 17:32                         ` Ingo Molnar
2009-04-03 17:32                           ` Ingo Molnar
2009-04-03 17:36                         ` Chris Wright
2009-04-03 17:39                           ` Ingo Molnar [this message]
2009-04-03 17:39                             ` Ingo Molnar
2009-04-03 17:39                             ` Ingo Molnar
2009-04-03 17:45                             ` Chris Wright
2009-04-07  8:54                               ` Arkadiusz Miskiewicz

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=20090403173955.GD6295@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.miskiewicz@gmail.com \
    --cc=chrisw@sous-sol.org \
    --cc=jeremy@xensource.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=travis@sgi.com \
    --cc=venkatesh.pallipadi@intel.com \
    --cc=virtualization@lists.osdl.org \
    --cc=xen-devel@lists.xensource.com \
    --cc=yhlu.kernel@gmail.com \
    /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.