From: Andrew Morton <akpm@linux-foundation.org>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
esandeen@redhat.com
Subject: Re: Unnecessary overhead with stack protector.
Date: Mon, 26 Oct 2009 09:37:06 -0700 [thread overview]
Message-ID: <20091026093706.c6416715.akpm@linux-foundation.org> (raw)
In-Reply-To: <20091026123004.297a0a25@katamari.usersys.redhat.com>
On Mon, 26 Oct 2009 12:30:04 -0400 Chuck Ebbert <cebbert@redhat.com> wrote:
> On Wed, 21 Oct 2009 18:26:36 -0700
> Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > On Thu, 15 Oct 2009 14:35:41 -0400 Dave Jones <davej@redhat.com> wrote:
> >
> > > 113c5413cf9051cc50b88befdc42e3402bb92115 introduced a change that
> > > made CC_STACKPROTECTOR_ALL not-selectable if someone enables CC_STACKPROTECTOR.
> > >
> > > We've noticed in Fedora that this has introduced noticable overhead on
> > > some functions, including those which don't even have any on-stack variables.
> > >
> > > According to the gcc manpage, -fstack-protector will protect functions with
> > > as little as 8 bytes of stack usage. So we're introducing a huge amount
> > > of overhead, to close a small amount of vulnerability (the >0 && <8 case).
> > >
> > > The overhead as it stands right now means this whole option is unusable for
> > > a distro kernel without reverting the above commit.
> > >
> >
> > This looks like a fairly serious problem to me, but I'm confused by the
> > commit ID. February 2008 - is this correct?
> >
>
> That date is pure fiction AFAICT. And the Mercurial kernel repo says May 2008...
> Is there some way to get the date a change was merged into the official tree as
> opposed to the date it was created in some other tree?
oh, so someone _did_ read my email!
git show --pretty=fuller 113c5413cf9051cc50b88befdc42e3402bb92115
commit 113c5413cf9051cc50b88befdc42e3402bb92115
Author: Ingo Molnar <mingo@elte.hu>
AuthorDate: Thu Feb 14 10:36:03 2008 +0100
Commit: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Mon May 26 16:15:32 2008 +0200
I think the CommitDate is when it hit mainline.
next prev parent reply other threads:[~2009-10-26 16:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 18:35 Unnecessary overhead with stack protector Dave Jones
2009-10-15 19:07 ` Ingo Molnar
2009-10-21 15:50 ` Eric Sandeen
2009-10-21 18:00 ` Arjan van de Ven
2009-10-21 18:59 ` Eric Sandeen
2009-10-21 19:09 ` Eric Sandeen
2009-10-21 19:24 ` Eric Sandeen
2009-10-21 21:08 ` Chuck Ebbert
2009-10-21 19:16 ` XFS stack overhead Ingo Molnar
2009-10-21 19:21 ` Eric Sandeen
2009-10-21 20:22 ` Chuck Ebbert
2009-10-22 1:26 ` Unnecessary overhead with stack protector Andrew Morton
2009-10-26 16:30 ` Chuck Ebbert
2009-10-26 16:37 ` Andrew Morton [this message]
2009-10-26 16:56 ` Chuck Ebbert
2009-10-26 20:03 ` Ingo Molnar
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=20091026093706.c6416715.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cebbert@redhat.com \
--cc=davej@redhat.com \
--cc=esandeen@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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.