From: Ingo Molnar <mingo@elte.hu>
To: pageexec@freemail.hu
Cc: Sam Ravnborg <sam@ravnborg.org>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: vmsplice exploits, stack protector and Makefiles
Date: Wed, 13 Feb 2008 16:29:00 +0100 [thread overview]
Message-ID: <20080213152900.GA28959@elte.hu> (raw)
In-Reply-To: <47B30F05.29637.9A21F9B@pageexec.freemail.hu>
* pageexec@freemail.hu <pageexec@freemail.hu> wrote:
> patches to get CONFIG_CC_STACKPROTECTOR_ALL actually to work (it
> includes the Makefile patch proposed in this thread already).
>
> note that the fix to ACPI is an actual stack corruption bug (caught by
> ssp thanks to a lucky stack layout), due to the misuse of the pci
> accessor functions, probably a whole-tree audit is in order for
> similar bugs.
>
> note also that the vsyscall functions (more precisely, all the code
> that goes into .vsyscall* sections) had better be separated into their
> own .c files so that they can be compiled without -mcmodel=kernel and
> use %fs for getting the ssp cookie, if ssp is desired at all there).
thanks, i've picked up your patch into x86.git#mm and also made
stackprotector-all default-enabled so that we get more test coverage of
this critical security feature. x86.git#mm can be picked up via:
http://people.redhat.com/mingo/x86.git/README
head of the tree:
---------------->
commit e1d96d3e489d02b12984fb3c755b0f9a9ae0fe5f
Author: Ingo Molnar <mingo@elte.hu>
Date: Wed Feb 13 16:15:34 2008 +0100
x86: enable stack-protector by default
also enable the rodata and nx tests.
<----------------
your patch booted fine here with stackprotector-all enabled.
Ingo
next prev parent reply other threads:[~2008-02-13 15:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 17:00 Arjan van de Ven
2008-02-12 18:50 ` Sam Ravnborg
2008-02-12 19:08 ` Arjan van de Ven
2008-02-12 19:36 ` Sam Ravnborg
2008-02-13 13:38 ` pageexec
2008-02-13 15:29 ` Ingo Molnar [this message]
2008-02-13 16:29 ` Randy Dunlap
2008-02-13 15:48 ` pageexec
2008-02-14 12:20 ` Jan Engelhardt
2008-02-13 16:48 ` Ingo Molnar
2008-02-13 16:15 ` pageexec
2008-02-14 6:16 ` Ingo Molnar
2008-02-14 7:30 ` Ingo Molnar
2008-02-14 10:23 ` pageexec
2008-02-13 15:53 ` Linus Torvalds
2008-02-13 16:01 ` Ingo Molnar
2008-02-13 17:16 ` Sam Ravnborg
2008-02-14 6:12 ` Ingo Molnar
2008-02-14 7:43 ` Sam Ravnborg
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=20080213152900.GA28959@elte.hu \
--to=mingo@elte.hu \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pageexec@freemail.hu \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.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 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®