All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: stable <stable@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Kees Cook <keescook@chromium.org>,
	John Stultz <john.stultz@linaro.org>
Subject: Re: [stable] Removing or restricting timer_stats
Date: Wed, 19 Apr 2017 13:50:18 +0200	[thread overview]
Message-ID: <20170419115018.GH27378@kroah.com> (raw)
In-Reply-To: <1492482305.2409.135.camel@decadent.org.uk>

On Tue, Apr 18, 2017 at 03:25:05AM +0100, Ben Hutchings wrote:
> The timer_stats feature was removed upstream by:
> 
> commit dfb4357da6ddbdf57d583ba64361c9d792b0e0b1
> Author: Kees Cook <keescook@chromium.org>
> Date:���Wed Feb 8 11:26:59 2017 -0800
> 
> ����time: Remove CONFIG_TIMER_STATS
> 
> I'm hesitant to propose removing a feature in stable, even if it is
> redundant.  What I've done for Debian stable is to restrict it to the
> initial pid namespace (see attached).  Would that be a reasonable
> alternative change for stable branches?

I don't mind removing things in stable as that's what happened in
Linus's tree, and it was removed for a reason.  We've done it before,
and I'm more hesitant to apply something that works a bit
"differently".

Kees, any objection for me just taking the "full" patch in the stable
kernels?

thanks,

greg k-h

  parent reply	other threads:[~2017-04-19 11:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18  2:25 [stable] Removing or restricting timer_stats Ben Hutchings
2017-04-18  3:38 ` Kees Cook
2017-04-19 11:50 ` Greg KH [this message]
2017-04-19 14:54   ` Kees Cook
2017-04-19 14:57     ` Greg KH
2017-04-19 15:01       ` Kees Cook
2017-04-19 15:18         ` Greg KH
2017-04-19 15:25         ` Arjan van de Ven
2017-04-19 15:37           ` Greg KH
2017-04-19 16:20             ` Kees Cook

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=20170419115018.GH27378@kroah.com \
    --to=greg@kroah.com \
    --cc=ben@decadent.org.uk \
    --cc=john.stultz@linaro.org \
    --cc=keescook@chromium.org \
    --cc=stable@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 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.