All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Thumshirn <jthumshirn@suse.de>
To: John Garry <john.garry@huawei.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
	James Bottomley <jejb@linux.vnet.ibm.com>,
	Linux SCSI Mailinglist <linux-scsi@vger.kernel.org>,
	Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
	Linuxarm <linuxarm@huawei.com>, Hannes Reinecke <hare@suse.de>,
	Jinpu Wang <jinpu.wang@profitbricks.com>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] scsi: sas: move scsi_remove_host call into sas_remove_host
Date: Mon, 24 Apr 2017 15:52:45 +0200	[thread overview]
Message-ID: <20170424134642.GD29543@linux-x5ow.site> (raw)
In-Reply-To: <e90738ea-185a-2c29-3542-c40057d46b6f@huawei.com>

On Mon, Apr 24, 2017 at 02:38:40PM +0100, John Garry wrote:
> On 24/04/2017 11:09, John Garry wrote:
> >On 21/04/2017 13:11, Johannes Thumshirn wrote:
> >>Move scsi_remove_host call into sas_remove_host and remove it from SAS
> >>HBA
> >>drivers, so we don't mess up the ordering. This solves an issue with
> >>double
> >>deleting sysfs entries that was introduced by the change of sysfs
> >>behaviour
> >>from commit bcdde7e ("sysfs: make __sysfs_remove_dir() recursive").
> >>
> >>Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
> >>Suggested-by: Christoph Hellwig <hch@lst.de>
> >>Cc: Hannes Reinecke <hare@suse.de>
> >>Cc: James Bottomley <jejb@linux.vnet.ibm.com>
> >>Cc: Jinpu Wang <jinpu.wang@profitbricks.com>
> >>Cc: John Garry <john.garry@huawei.com>
> >
> >For what it's worth:
> >
> >Tested-by: John Garry <john.garry@huawei.com> # On hisi_sas
> >
> 
> I have actually tested this a little further and now I see an issue. Maybe
> it is related to the internal development kernel I am using or a
> pre-existing issue with our driver, but I doubt it.
> This time I removed the WARN in sysfs_remove_group() [so the console is not
> bombarded] and ran repeated insmod/rmmod, and I see this sometimes:

[...]


> Ring any bells? I don't see this new WARN without the change.

No haven't seen the WARN in my tests but I didn't do a insmod/rmmod stress
test anyways.

I'll have a look.

-- 
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

      reply	other threads:[~2017-04-24 13:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21 12:11 [PATCH] scsi: sas: move scsi_remove_host call into sas_remove_host Johannes Thumshirn
2017-04-21 12:49 ` Christoph Hellwig
2017-04-21 13:00 ` Jinpu Wang
2017-04-21 14:37 ` Martin K. Petersen
2017-04-24  9:14 ` Hannes Reinecke
2017-04-24 10:09 ` John Garry
2017-04-24 13:38   ` John Garry
2017-04-24 13:38     ` John Garry
2017-04-24 13:52     ` Johannes Thumshirn [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=20170424134642.GD29543@linux-x5ow.site \
    --to=jthumshirn@suse.de \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=jinpu.wang@profitbricks.com \
    --cc=john.garry@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=martin.petersen@oracle.com \
    /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.