linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: "Ewan D. Milne" <emilne@redhat.com>,
	Hannes Reinecke <hare@suse.com>,
	James Bottomley <jejb@linux.vnet.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org, linux-next@vger.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: [-next] BUG_ON in scsi_target_destroy()
Date: Mon, 11 Apr 2016 18:01:47 +0900	[thread overview]
Message-ID: <20160411090146.GA537@swordfish> (raw)

Hello,

commit 7b106f2de6938c31ce5e9c86bc70ad3904666b96
Author: Johannes Thumshirn <jthumshirn@suse.de>
Date:   Tue Apr 5 11:50:44 2016 +0200

    scsi: Add intermediate STARGET_REMOVE state to scsi_target_state


BUG_ON()s (next-20160411) each time I remove a usb flash

[   49.561600]  [<ffffffffa0087f42>] scsi_target_destroy+0x5a/0xcb [scsi_mod]
[   49.561607]  [<ffffffffa0089099>] scsi_target_reap+0x4a/0x4f [scsi_mod]
[   49.561613]  [<ffffffffa008b453>] __scsi_remove_device+0xc3/0xd0 [scsi_mod]
[   49.561619]  [<ffffffffa0089d7b>] scsi_forget_host+0x52/0x63 [scsi_mod]
[   49.561623]  [<ffffffffa0080dbc>] scsi_remove_host+0x8c/0x102 [scsi_mod]
[   49.561627]  [<ffffffffa015c447>] usb_stor_disconnect+0x6b/0xab [usb_storage]
[   49.561634]  [<ffffffffa0013f73>] usb_unbind_interface+0x77/0x1ca [usbcore]
[   49.561636]  [<ffffffff813ae064>] __device_release_driver+0x9d/0x121
[   49.561638]  [<ffffffff813ae10b>] device_release_driver+0x23/0x30
[   49.561639]  [<ffffffff813ad2d1>] bus_remove_device+0xfb/0x10e
[   49.561641]  [<ffffffff813aac05>] device_del+0x164/0x1e6
[   49.561648]  [<ffffffffa0011b09>] ? remove_intf_ep_devs+0x3b/0x48 [usbcore]
[   49.561655]  [<ffffffffa001200e>] usb_disable_device+0x84/0x1a5 [usbcore]
[   49.561661]  [<ffffffffa000ac7b>] usb_disconnect+0x94/0x19f [usbcore]
[   49.561667]  [<ffffffffa000c2ab>] hub_event+0x5c1/0xdea [usbcore]
[   49.561670]  [<ffffffff810530b1>] process_one_work+0x1dc/0x37f
[   49.561672]  [<ffffffff81053dc5>] worker_thread+0x282/0x36d
[   49.561673]  [<ffffffff81053b43>] ? rescuer_thread+0x2ae/0x2ae
[   49.561675]  [<ffffffff810580a8>] kthread+0xd2/0xda
[   49.561678]  [<ffffffff814bbf92>] ret_from_fork+0x22/0x40
[   49.561679]  [<ffffffff81057fd6>] ? kthread_worker_fn+0x13e/0x13e

	-ss

             reply	other threads:[~2016-04-11  9:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11  9:01 Sergey Senozhatsky [this message]
2016-04-13  8:41 ` [-next] BUG_ON in scsi_target_destroy() Johannes Thumshirn
2016-04-13 14:47   ` Sergey Senozhatsky
2016-04-13 13:59     ` Johannes Thumshirn
2016-04-13 15:14   ` James Bottomley
2016-04-14  2:07     ` Sergey Senozhatsky
2016-04-15  5:53     ` Xiong Zhou
2016-04-15 20:55     ` Martin K. Petersen
2016-04-15  4:31   ` Xiong Zhou

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=20160411090146.GA537@swordfish \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=emilne@redhat.com \
    --cc=hare@suse.com \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=jthumshirn@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=sfr@canb.auug.org.au \
    /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).