All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Dave Jones <davej@redhat.com>, Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org, sam@ravnborg.org,
	arjan@infradead.org, stable@kernel.org,
	stable-commits@vger.kernel.org
Subject: Re: [stable] patch kbuild-allow-fstack-protector-to-take-effect.patch added to 2.6.24-stable tree
Date: Fri, 22 Feb 2008 17:08:16 -0800	[thread overview]
Message-ID: <20080223010816.GA4754@suse.de> (raw)
In-Reply-To: <20080222235914.GC20829@redhat.com>

On Fri, Feb 22, 2008 at 06:59:14PM -0500, Dave Jones wrote:
> On Fri, Feb 22, 2008 at 03:42:16PM -0800, Greg Kroah-Hartman wrote:
> 
>  > >  > I thought that thread was for the much larger patches, not just this
>  > >  > Makefile change.
>  > > 
>  > > At the least we'll likely want to also pick up the other stack protector fixes
>  > > that went into .25rc if we turn it on in .24
>  > 
>  > Hm, that sounds like a new feature :)
>  > 
>  > I thought the makefile change was just a bugfix in the broken makefile.
> 
> Well, it is. But it'll cause it to enable something that has been broken for a while.
> FWIW, I think having the stack protector reenabled in -stable is a worthwhile goal,
> but only once it's stabilised for a while in the development tree.
> 
> My fear by just reenabling this for -stable is that when distros push out updates
> based on the latest -stable, we'll see more systems like James' problematic system.

Fair enough, between this worry, and Arjan saying "no way", I've now
dropped it :)

thanks,

greg k-h

      reply	other threads:[~2008-02-23  1:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200802190005.m1J05SKP017015@hera.kernel.org>
     [not found] ` <20080222230103.CC4EF14540D0@imap.suse.de>
2008-02-22 23:06   ` patch kbuild-allow-fstack-protector-to-take-effect.patch added to 2.6.24-stable tree Dave Jones
2008-02-22 23:18     ` [stable] " Greg KH
2008-02-22 23:34       ` Dave Jones
2008-02-22 23:42         ` Greg KH
2008-02-22 23:59           ` Dave Jones
2008-02-23  1:08             ` Greg KH [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=20080223010816.GA4754@suse.de \
    --to=gregkh@suse.de \
    --cc=arjan@infradead.org \
    --cc=davej@redhat.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@kernel.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 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.