public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Greg KH <greg@kroah.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] reboot: disable usermodehelper to prevent fs access
Date: Thu, 05 May 2011 20:04:46 -0400	[thread overview]
Message-ID: <45795.1304640286@localhost> (raw)
In-Reply-To: Your message of "Thu, 05 May 2011 14:34:58 PDT." <20110505213458.GA4331@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]

On Thu, 05 May 2011 14:34:58 PDT, Greg KH said:
> On Thu, May 05, 2011 at 05:24:25PM -0400, Valdis.Kletnieks@vt.edu wrote:
> > On Thu, 05 May 2011 13:32:05 +0200, Kay Sievers said:
> > > In case CONFIG_UEVENT_HELPER_PATH is not set to "", which it
> > > should be on every system
> >
> > If it indeed should be that on every system, shouldn't it be listed
> > in feature-removal-schedule.txt?
>
> It's the default value, but distros, and people, can and do override it
> for various reasons.  Why would it be added to
> feature-removal-schedule.txt?

Well, what Kay said was "it should be on *every* system", making it sound like
it's an option past its shelf life.  Certainly, "the default should be null for
the vast majority of systems" is a different scenario.

> > Does anybody have a running list of "Stuff we set by default at one time, but
> > no longer recommend"?

> Look at the default values for different configurations options and why
> they differ in your system is about the only way that I know of, sorry.

Hmm.. I suspect diffconfig will only get me part of the way there.  Maybe what
I *need* to do is find a 2.6.25-ish x86_64 defconfig, the current one, diff those, and
then see what changed (as opposed to truly new config flags), and then see
how many of those changes do/don't show up in *my* config as well..

Maybe that would be a good project for some #kernelnewbie to look at ;)
"In my copious free time" ;)


[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2011-05-06  0:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05 11:32 [PATCH] reboot: disable usermodehelper to prevent fs access Kay Sievers
2011-05-05 20:27 ` Greg KH
2011-05-06  1:15   ` Kay Sievers
2011-05-05 21:24 ` Valdis.Kletnieks
2011-05-05 21:34   ` Greg KH
2011-05-06  0:04     ` Valdis.Kletnieks [this message]
2011-05-06  1:07       ` Kay Sievers

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=45795.1304640286@localhost \
    --to=valdis.kletnieks@vt.edu \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox