[lkml]   [2011]   [Nov]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Kgdb-bugreport] [PATCH v2 3/3] param: make /sys/module/*/paramaters optional
On 11/2/2011 6:30 AM, Jason Wessel wrote:
> On 11/01/2011 06:50 PM, David Decotigny wrote:
>> From: David Decotigny<>
>> 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

 \ /
  Last update: 2011-11-02 17:27    [W:0.049 / U:6.652 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site