From: Chris Wright <chrisw@sous-sol.org>
To: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Ingo Molnar <mingo@elte.hu>,
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 10:36:31 -0700 [thread overview]
Message-ID: <20090403173631.GA27148@sequoia.sous-sol.org> (raw)
In-Reply-To: <200904030847.19674.a.miskiewicz@gmail.com>
* 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:
From: Joseph Cihula <joseph.cihula@intel.com>
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>
--- ../linux.trees.git/arch/x86/power/Makefile 2009-03-29
12:12:13.000000000 -0700
+++ arch/x86/power/Makefile 2009-03-30 12:21:19.000000000 -0700
@@ -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
next prev parent reply other threads:[~2009-04-03 17:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 9:55 Arkadiusz Miskiewicz
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: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-02 21:00 ` Rafael J. Wysocki
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 6:47 ` Arkadiusz Miskiewicz
2009-04-03 17:32 ` Ingo Molnar
2009-04-03 17:36 ` Chris Wright [this message]
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=20090403173631.GA27148@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=a.miskiewicz@gmail.com \
--cc=jeremy@xensource.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®