From: Johannes Thumshirn <jthumshirn@suse.de>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
"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,
Xiong Zhou <jencce.kernel@gmail.com>
Subject: Re: [-next] BUG_ON in scsi_target_destroy()
Date: Wed, 13 Apr 2016 15:59:31 +0200 [thread overview]
Message-ID: <1517391.Uqi4c4PsRt@c203> (raw)
In-Reply-To: <20160413144704.GA490@swordfish>
On Mittwoch, 13. April 2016 23:47:04 CEST Sergey Senozhatsky wrote:
> Hi,
>
> On (04/13/16 10:41), Johannes Thumshirn wrote:
> > Hi Sergey, Xiong,
> >
> > Can you try below patch?
>
> it panics my system.
> first it warn_on-s in lib/kobject.c:244
>
> then NULL dereferences
> do_scan_async
> __scsi_remove_device
> scsi_target_reap
> device_del
> dpm_sysfs_remove
> sysfs_unmerge_group
> kernfs_find_and_get_ns
> kernfs_find_ns
>
> -ss
>
Thanks for the update, I'll have a look into the callchain
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2016-04-13 13:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 9:01 [-next] BUG_ON in scsi_target_destroy() Sergey Senozhatsky
2016-04-13 8:41 ` Johannes Thumshirn
2016-04-13 8:41 ` Johannes Thumshirn
2016-04-13 14:47 ` Sergey Senozhatsky
2016-04-13 13:59 ` Johannes Thumshirn [this message]
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
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=1517391.Uqi4c4PsRt@c203 \
--to=jthumshirn@suse.de \
--cc=emilne@redhat.com \
--cc=hare@suse.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=jencce.kernel@gmail.com \
--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.work@gmail.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 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.