public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: "Andi Kleen" <andi@firstfloor.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] Move sysctl check into debugging section and don't make it default y
Date: Wed, 20 Aug 2008 23:14:36 -0700	[thread overview]
Message-ID: <m1myj63neb.fsf@frodo.ebiederm.org> (raw)
In-Reply-To: <1218865985-23403-1-git-send-email-andi@firstfloor.org> (Andi Kleen's message of "Sat, 16 Aug 2008 07:53:05 +0200")

"Andi Kleen" <andi@firstfloor.org> writes:

> From: Andi Kleen <ak@linux.intel.com>
>
> I noticed that sysctl_check.o was the largest object file in
> a allnoconfig build in kernel/*.
>
>   36243       0       0   36243    8d93 kernel/sysctl_check.o
>
> This is because it was default y and && EMBEDDED. But I don't
> really see a need for a non kernel developer to have their
> sysctls checked all the time.

What is a feature change like this doing coming in after the
merge window?

Why doesn't an allnoconfig disable sysctl all together?

> So move the Kconfig into the kernel debugging section and
> also drop the default y and the EMBEDDED check.

Which is an idiotic thing to do.

These are the only checks we have against someone doing something
nasty in the sysctl hierarchy.   We have proven that we don't
have the discipline to do the right thing with code in the
core kernel.  I expect out of tree code will be much worse.

Eric

  reply	other threads:[~2008-08-21  6:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-16  5:53 [PATCH] Move sysctl check into debugging section and don't make it default y Andi Kleen
2008-08-21  6:14 ` Eric W. Biederman [this message]
2008-08-21  6:40   ` Andi Kleen
2008-08-21  8:14     ` Eric W. Biederman
2008-08-21 18:15     ` Eric W. Biederman
2008-08-22  1:57       ` Andi Kleen
2008-08-22  2:17         ` Eric W. Biederman

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=m1myj63neb.fsf@frodo.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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