From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "hare@suse.de" <hare@suse.de>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH v2] scsi_sysfs: fix hang when removing scsi device
Date: Sat, 18 Mar 2017 00:05:10 +0000 [thread overview]
Message-ID: <1489795496.2826.25.camel@sandisk.com> (raw)
In-Reply-To: <1489705225.2574.22.camel@sandisk.com>
On Thu, 2017-03-16 at 23:00 +0000, Bart Van Assche wrote:
> The following crash only occurs with async aborts enabled:
>
> general protection fault: 0000 [#1] SMP
> RIP: 0010:scsi_device_put+0xb/0x30
> Call Trace:
> scsi_disk_put+0x2d/0x40
> sd_release+0x3d/0xb0
> __blkdev_put+0x29e/0x360
> blkdev_put+0x49/0x170
> dm_put_table_device+0x58/0xc0 [dm_mod]
> dm_put_device+0x70/0xc0 [dm_mod]
> free_priority_group+0x92/0xc0 [dm_multipath]
> free_multipath+0x70/0xc0 [dm_multipath]
> multipath_dtr+0x19/0x20 [dm_multipath]
> dm_table_destroy+0x67/0x120 [dm_mod]
> dev_suspend+0xde/0x240 [dm_mod]
> ctl_ioctl+0x1f5/0x520 [dm_mod]
> dm_ctl_ioctl+0xe/0x20 [dm_mod]
> do_vfs_ioctl+0x8f/0x700
> SyS_ioctl+0x3c/0x70
> entry_SYSCALL_64_fastpath+0x18/0xad
(replying to my own e-mail)
With my three scsi_dh_alua patches applied I don't see this crash anymore so
this crash was probably unrelated to async aborts.
Bart.
next prev parent reply other threads:[~2017-03-18 0:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 16:37 [PATCH v2] scsi_sysfs: fix hang when removing scsi device Israel Rukshin
2017-03-09 19:36 ` Bart Van Assche
2017-03-12 10:26 ` Israel Rukshin
2017-03-13 18:49 ` Bart Van Assche
2017-03-13 19:23 ` James Bottomley
2017-03-13 20:33 ` Bart Van Assche
2017-03-13 21:55 ` James Bottomley
2017-03-14 2:35 ` Bart Van Assche
2017-03-14 9:44 ` Israel Rukshin
2017-03-14 14:23 ` Israel Rukshin
2017-03-15 23:27 ` Bart Van Assche
2017-03-16 9:02 ` Israel Rukshin
2017-03-16 15:42 ` Bart Van Assche
2017-03-16 15:59 ` Israel Rukshin
2017-03-16 23:00 ` Bart Van Assche
2017-03-18 0:05 ` Bart Van Assche [this message]
2017-03-18 11:17 ` Hannes Reinecke
2017-03-18 15:28 ` Bart Van Assche
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=1489795496.2826.25.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.