From: Greg KH <greg@kroah.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
Chuck Ebbert <cebbert@redhat.com>,
USB development list <linux-usb-devel@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: blank filenames in /sys/modules, kernel 2.6.21
Date: Fri, 8 Jun 2007 12:02:13 -0700 [thread overview]
Message-ID: <20070608190213.GA14586@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706081440340.9344@localhost.localdomain>
On Fri, Jun 08, 2007 at 02:44:12PM -0400, Robert P. J. Day wrote:
> On Fri, 8 Jun 2007, Greg KH wrote:
>
> > On Fri, Jun 08, 2007 at 02:05:22PM -0400, Robert P. J. Day wrote:
> > > On Fri, 8 Jun 2007, Chuck Ebbert wrote:
> > >
> > > > We just found a file with this name in 2.6.21:
> > > >
> > > > Directory name: /sys/module/nousb/parameters
> > > > File name: ""
> > > >
> > > > IOW the file has an empty name. Is this intentional?
> > > > It sure confuses updatedb...
> > > >
> > > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242715
> > >
> > > that appears to be the result of:
> > >
> > > $ grep -r __module_param_call *
> > > drivers/usb/core/usb.c:__module_param_call("", nousb, param_set_bool, param_get_bool, &nousb, 0444);
> > > include/linux/moduleparam.h:#define __module_param_call(prefix, name, set, get, arg, perm) \
> > > include/linux/moduleparam.h: __module_param_call(MODULE_PARAM_PREFIX, name, set, get, arg, perm)
> > >
> > > and from drivers/usb/core/usb.c:
> > >
> > > /* format to disable USB on kernel command line is: nousb */
> > > __module_param_call("", nousb, param_set_bool, param_get_bool, &nousb, 0444);
> > >
> > > one has to wonder about the value of a macro that is invoked only
> > > once throughout the entire tree.
> >
> > Pete added that back in December of 2005 (git-blame rocks...). So what
> > has changed recently to cause this to do different things in sysfs?
> >
> > Robert, what do you suggest we change this usage to look like?
>
> um ... i'm fairly sure i'm totally the wrong person to be asked about
> this, but what does any of the above have to do with disabling USB on
> the kernel command line? wouldn't you typically define a kernel
> command line option with something like:
> ...
> arch/i386/kernel/traps.c:__setup("kstack=", kstack_setup);
> arch/i386/kernel/traps.c:__setup("code_bytes=", code_bytes_setup);
> arch/i386/kernel/nmi.c:__setup("nmi_watchdog=", setup_nmi_watchdog);
> arch/i386/kernel/reboot.c:__setup("reboot=", reboot_setup);
> arch/i386/kernel/tsc.c:__setup("notsc", tsc_setup);
> ...
>
> you know -- that sort of thing. i mean, that's where *i'd* introduce
> a "nousb" option.
It's a module parameter as well as a kernel command line option, see
Pete's response.
thanks,
greg k-h
next prev parent reply other threads:[~2007-06-08 19:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 18:00 blank filenames in /sys/modules, kernel 2.6.21 Chuck Ebbert
2007-06-08 18:05 ` Robert P. J. Day
2007-06-08 18:32 ` Greg KH
2007-06-08 18:44 ` Robert P. J. Day
2007-06-08 19:02 ` Greg KH [this message]
2007-06-08 18:48 ` Pete Zaitcev
2007-06-08 18:48 ` Robert P. J. Day
2007-06-08 18:07 ` Greg KH
2007-06-08 22:50 ` Chuck Ebbert
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=20070608190213.GA14586@kroah.com \
--to=greg@kroah.com \
--cc=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=rpjday@mindspring.com \
--cc=zaitcev@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox