From: Greg KH <gregkh@suse.de>
To: Dave Airlie <airlied@gmail.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
Jeff Chua <jeff.chua.linux@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Scott James Remnant <scott@canonical.com>,
Dave Jones <davej@redhat.com>, Peter Jones <pjones@redhat.com>
Subject: Re: can we move USB_DEVICEFS to non-embedded?
Date: Wed, 8 Jul 2009 06:00:56 -0700 [thread overview]
Message-ID: <20090708130056.GA19543@suse.de> (raw)
In-Reply-To: <21d7e9970907080420h41375e36q1efacb9f3555b9de@mail.gmail.com>
On Wed, Jul 08, 2009 at 09:20:04PM +1000, Dave Airlie wrote:
> On Wed, Jul 8, 2009 at 9:03 PM, Kay Sievers<kay.sievers@vrfy.org> wrote:
> > On Wed, Jul 8, 2009 at 12:54, Dave Airlie<airlied@gmail.com> wrote:
> >
> >> Okay can we revert this for a better reason? it seems to have unhidden a race
> >> condition on booting some of my machines. I've booted some other machines
> >> with the same USB disk and the same kernel fine.
> >
> > Are you sure? USBFS is for userspace USB drivers, booting from
> > usb-storage devices should be fully handled by the kernel.
> >
>
> Yes, changing just this option means the difference between a bootable
> and stuck in initrd system. maybe Peter knows if our initrd does something
> otherwise I suspect we have a race that usbfs was hiding.
Like Kay stated, this sounds very strange, I'd like to find out the root
cause of this before reverting the config option. Nothing at startup
should be using/needing usbfs that I can think of.
thanks,
greg k-h
next prev parent reply other threads:[~2009-07-08 13:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 5:11 can we move USB_DEVICEFS to non-embedded? Jeff Chua
2009-06-23 8:17 ` Scott James Remnant
2009-06-23 14:42 ` Greg KH
2009-06-23 15:29 ` Jeff Chua
2009-06-23 15:39 ` Greg KH
2009-07-08 10:54 ` Dave Airlie
2009-07-08 11:03 ` Kay Sievers
2009-07-08 11:20 ` Dave Airlie
2009-07-08 11:42 ` Scott James Remnant
2009-07-08 13:00 ` Greg KH [this message]
2009-07-08 13:52 ` Peter Jones
2009-07-08 13:55 ` Peter Jones
2009-07-08 14:04 ` Greg KH
2009-07-08 14:12 ` Peter Jones
2009-07-08 14:56 ` Greg KH
2009-07-08 15:05 ` Peter Jones
2009-07-08 15:47 ` Greg KH
2009-07-08 21:23 ` Dave Airlie
2009-07-09 0:43 ` Jeff Chua
2009-07-09 1:59 ` Randy Dunlap
2009-07-09 2:31 ` Jeff Chua
2009-07-09 3:01 ` Randy Dunlap
2009-07-09 12:12 ` Jeff Chua
2009-07-09 1:33 ` Greg KH
2009-07-08 15:12 ` Bill Nottingham
2009-07-08 15:44 ` Greg KH
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=20090708130056.GA19543@suse.de \
--to=gregkh@suse.de \
--cc=airlied@gmail.com \
--cc=davej@redhat.com \
--cc=jeff.chua.linux@gmail.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pjones@redhat.com \
--cc=scott@canonical.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).