linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Chris Mason <chris.mason@fusionio.com>,
	linux-btrfs@vger.kernel.org, linux-usb@vger.kernel.org,
	Hans de Goede <hdegoede@redhat.com>,
	linux-scsi@vger.kernel.org
Subject: Re: BTRFS doesn't handle USB device disconnect
Date: Wed, 11 Dec 2013 15:20:05 -0800	[thread overview]
Message-ID: <20131211232005.GA2620@xanatos> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1312111058340.1531-100000@iolanthe.rowland.org>

On Wed, Dec 11, 2013 at 11:03:09AM -0500, Alan Stern wrote:
> On Tue, 10 Dec 2013, Sarah Sharp wrote:
> > On 3.13-rc1, the btrfs partion from the disconnected USB device
> > continues to be listed as mounted.  Yanking the cable produces some
> > additional oops messages.  It also produced a couple hard-hangs.
> > Unfortunately, I didn't capture the dmesg during the hard-hangs, so I
> > can't tell for sure which driver is to blame (uas, btrfs, or xhci).
> 
> Does this happen with usb-storage instead of uas?
> 
> What about with ehci-hcd instead of xhci-hcd?
> 
> And just to be exotic, what about with dummy-hcd and the uas or
> g_mass_storage gadget driver?

I can't reproduce the hard-hangs (with xhci and uas), but I did manage
to reproduce a bug in uas where the disconnect function hangs, and hangs
the khubd thread as well.  This happens even with the btrfs partition
wiped from the drive, so it's not a btrfs issue.  I'll send a separate
bug report to Hans.

Sarah Sharp

      parent reply	other threads:[~2013-12-11 23:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20131211011755.GA3574@xanatos>
2013-12-11 16:03 ` BTRFS doesn't handle USB device disconnect Alan Stern
2013-12-11 16:18   ` Hugo Mills
2013-12-11 23:20   ` Sarah Sharp [this message]

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=20131211232005.GA2620@xanatos \
    --to=sarah.a.sharp@linux.intel.com \
    --cc=chris.mason@fusionio.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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).