All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: David Decotigny <david.decotigny@google.com>,
	Kroah-Hartman <gregkh@suse.de>,
	Linus Walleij <linus.walleij@stericsson.com>,
	"Richard@mail2.fw-bc.sony.com" <Richard@mail2.fw-bc.sony.com>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	Lucas De Marchi <lucas.demarchi@profusion.mobi>,
	"kgdb-bugreport@lists.sourceforge.net" 
	<kgdb-bugreport@lists.sourceforge.net>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Dmitry Torokhov <dtor@vmware.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Michal Schmidt <mschmidt@redhat.com>,
	"David@mail2.fw-bc.sony.com" <David@mail2.fw-bc.sony.com>,
	Randy Dunlap <rdunlap@xenotime.net>,
	"Greg@mail2.fw-bc.sony.com" <Greg@mail2.fw-bc.sony.com>,
	Satoru Moriya <satoru.moriya@hds.com>,
	Sievers <kay.sievers@vrfy.org>, Decotigny <decot@google.com>,
	"Kay@mail2.fw-bc.sony.com" <Kay@mail2.fw-bc.sony.com>,
	Kennedy <richard@rsk.demon.co.uk>
Subject: Re: [Kgdb-bugreport] [PATCH v2 3/3] param: make	/sys/module/*/paramaters optional
Date: Wed, 2 Nov 2011 09:24:35 -0700	[thread overview]
Message-ID: <4EB16EC3.8020209@am.sony.com> (raw)
In-Reply-To: <4EB145FB.70906@windriver.com>

On 11/2/2011 6:30 AM, Jason Wessel wrote:
> On 11/01/2011 06:50 PM, David Decotigny wrote:
>> From: David Decotigny<decot@google.com>
>>
>> With this patch, we allow systems that don't want to pay the price for
>> /sys/module/*/paramaters to be compiled without that feature. This
>> abiltity can in turn encourage module developers to expose more of
>> their parameters with fewer hesitations (eg. memory concerns, etc.);
>> this is desirable to help debugging/auditing of live (larger) systems.
>>
>> The new knob to control that is CONFIG_SYSFS_MODULE_PARAM available in
>> Kconfig in expert mode: File systems / Pseudo filesystems / sysfs file
>> system support / Module parameters in sysfs. It is enabled by default,
>> keeping /sys/module/*/paramaters/ available as before.
>>
>> As an illustration, on my copy I see 1658 module_param() macros with
>> perm == 0: most of these could be exposed to user (perm != 0).
> Speaking as an embedded developer who works on very small systems that you can still debug, I am really curious what you actually save here?
>
> For dynamic kgdb/kdb this patch is a death sentence.  It would make us have to resurrect the procfs entries for the control point.  There is no possible way to dynamically turn kgdb on and off at all if you remove the /sys/module/kgdboc/parameters/kgdboc entry, and this is certainly something where the typical use case is dynamic enablement.
I would also like to see the size numbers.  However, to address
Jason's concern, I think it's safe to assume that when someone is
getting this aggressive with system size, they'll start leaving debug
features on the floor (printk, kdb, etc.).  What would be appropriate,
IMHO, would be to add a config dependency for kgdb/kdb and
NOT resurrect /proc items.  There's work in progress in linux-tiny
to tackle /proc configurability, and adding back /proc interfaces
is likely to just have the issue resurface there.
  -- Tim



  reply	other threads:[~2011-11-02 16:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-01 23:50 [PATCH v2 0/3] param: optional /sys/module/*/parameters David Decotigny
2011-11-01 23:50 ` [PATCH v2 1/3] param: make destroy_params() private David Decotigny
2011-11-01 23:50 ` [PATCH v2 2/3] param: simple refactoring David Decotigny
2011-11-01 23:50 ` [PATCH v2 3/3] param: make /sys/module/*/paramaters optional David Decotigny
2011-11-02  0:24   ` Greg KH
2011-11-02 23:02     ` David Decotigny
2011-11-03  1:29       ` Greg KH
2011-11-02 13:30   ` Jason Wessel
2011-11-02 16:24     ` Tim Bird [this message]
2011-11-02 21:51       ` [Kgdb-bugreport] " Rusty Russell

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=4EB16EC3.8020209@am.sony.com \
    --to=tim.bird@am.sony.com \
    --cc=David@mail2.fw-bc.sony.com \
    --cc=Greg@mail2.fw-bc.sony.com \
    --cc=Kay@mail2.fw-bc.sony.com \
    --cc=Richard@mail2.fw-bc.sony.com \
    --cc=david.decotigny@google.com \
    --cc=decot@google.com \
    --cc=dtor@vmware.com \
    --cc=gregkh@suse.de \
    --cc=jason.wessel@windriver.com \
    --cc=kay.sievers@vrfy.org \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucas.demarchi@profusion.mobi \
    --cc=mschmidt@redhat.com \
    --cc=rdunlap@xenotime.net \
    --cc=richard@rsk.demon.co.uk \
    --cc=rusty@rustcorp.com.au \
    --cc=satoru.moriya@hds.com \
    /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.