public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	esandeen@redhat.com
Subject: Re: Unnecessary overhead with stack protector.
Date: Mon, 26 Oct 2009 21:03:52 +0100	[thread overview]
Message-ID: <20091026200352.GA24682@elte.hu> (raw)
In-Reply-To: <20091026125615.6dcc1e0e@katamari.usersys.redhat.com>


* Chuck Ebbert <cebbert@redhat.com> wrote:

> On Mon, 26 Oct 2009 09:37:06 -0700
> Andrew Morton <akpm@linux-foundation.org> wrote:
> 
> > > > 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.
> 
> The X-Git-Tag from the web page says it first appeared in mainline in
> 2.6.30-rc1:
> 
> From: Ingo Molnar <mingo@elte.hu>
> Date: Thu, 14 Feb 2008 09:36:03 +0000 (+0100)
> Subject: x86: unify stackprotector features
> X-Git-Tag: v2.6.30-rc1~2^2~50^2~67^2~11
> X-Git-Url: http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Ftorvalds%2Flinux-2.6.git;a=commitdiff_plain;h=113c5413c
> 
> Looks like it went through three merges on the way there?

yep. Note that x86/urgent has this queued up now:

 14a3f40: x86: Remove STACKPROTECTOR_ALL

	Ingo

      reply	other threads:[~2009-10-26 20:04 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
2009-10-26 16:56       ` Chuck Ebbert
2009-10-26 20:03         ` Ingo Molnar [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=20091026200352.GA24682@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=cebbert@redhat.com \
    --cc=davej@redhat.com \
    --cc=esandeen@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox