From: Pete Zaitcev <zaitcev@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
USB development list <linux-usb-devel@lists.sourceforge.net>,
Chuck Ebbert <cebbert@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
zaitcev@redhat.com
Subject: Re: blank filenames in /sys/modules, kernel 2.6.21
Date: Fri, 8 Jun 2007 11:48:35 -0700 [thread overview]
Message-ID: <20070608114835.7a5af390.zaitcev@redhat.com> (raw)
In-Reply-To: <20070608183232.GA12967@kroah.com>
On Fri, 8 Jun 2007 11:32:32 -0700, Greg KH <greg@kroah.com> wrote:
> > 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);
> 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?
Aww. I thought it was a nice patch, but my foresight was inadequate.
The problem I tried to fix was related to strncmp used in the code which
supported __setup(). Our installer, Anaconda, recognizes both "nousb" and
"nousbstorage" - in theory. In practice, passing "nousbstorage" switched
USB completely off because of improper strncmp(). If we back out my patch,
this problem is going to reoccur.
We might want to ask Jeremy Katz if "nousbstorage" is even used anymore,
then revert all this if not. Or, we can add a name somehow and live
with it visible in sysfs...
-- Pete
next prev parent reply other threads:[~2007-06-08 18:48 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
2007-06-08 18:48 ` Pete Zaitcev [this message]
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=20070608114835.7a5af390.zaitcev@redhat.com \
--to=zaitcev@redhat.com \
--cc=cebbert@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=rpjday@mindspring.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