All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: John Garry <john.garry@huawei.com>
Cc: jejb@linux.vnet.ibm.com,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	wangyijing <wangyijing@huawei.com>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	John Garry <john.garry2@mail.dcu.ie>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linuxarm@huawei.com, lindar_liu@usish.com,
	Tejun Heo <tj@kernel.org>,
	Jinpu Wang <jinpu.wang@profitbricks.com>
Subject: Re: [RFC PATCH] scsi: libsas: fix WARN on device removal
Date: Thu, 17 Nov 2016 17:53:31 -0800	[thread overview]
Message-ID: <CAPcyv4g7_kDAZNZ2ikBRgFsX-hFpcXEV2xg9YS0Ha7PjSBkzVQ@mail.gmail.com> (raw)
In-Reply-To: <9bdd2ca5-aa72-6a18-b66d-8e791e4852c7@huawei.com>

On Thu, Nov 17, 2016 at 7:23 AM, John Garry <john.garry@huawei.com> wrote:
> On 11/11/2016 08:49, wangyijing wrote:
>>>>>
>>>>> I have not seen the flutter issue. I am just trying to solve the
>>>>> horrible WARN dump.
>>>>> However I do understand that there may be a issue related to how we
>>>>> queue the events; there was a recent attempt to fix this, but it came to
>>>>> nothing:
>>>>> https://www.spinics.net/lists/linux-scsi/msg99991.html
>>>>
>>>>
>>>> We found libsas hotplug several problems:
>>>> 1. sysfs warning calltrace(like the case you found);
>>>
>>>
>>> Maybe you can then review my patch.
>>
>>
>> I did it, I think your solution to fix the sysfs calltrace issue is ok,
>> and what I worried about is we still need to fix
>> the rest issues. So it's better if we could fix all issues one time.
>>
>
> @Maintainers, would you be willing to accept this patch as an interim fix
> for the dastardly WARN while we try to fix the flutter issue?

To me this adds a bug to quiet a benign, albeit noisy, warning.

  parent reply	other threads:[~2016-11-18  1:53 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03 14:58 [RFC PATCH] scsi: libsas: fix WARN on device removal John Garry
2016-11-03 14:58 ` John Garry
2016-11-09 12:28 ` John Garry
2016-11-09 12:28   ` John Garry
2016-11-09 17:36   ` John Garry
2016-11-09 17:36     ` John Garry
2016-11-09 19:09     ` Dan Williams
2016-11-09 20:35       ` Dan Williams
2016-11-10 11:53         ` John Garry
2016-11-10 11:53           ` John Garry
2016-11-11  8:12           ` wangyijing
2016-11-11  8:12             ` wangyijing
2016-11-11  8:23             ` John Garry
2016-11-11  8:23               ` John Garry
2016-11-11  8:49               ` wangyijing
2016-11-11  8:49                 ` wangyijing
2016-11-17 15:23                 ` John Garry
2016-11-17 15:23                   ` John Garry
2016-11-18  1:51                   ` Martin K. Petersen
2016-11-18  1:51                     ` Martin K. Petersen
2016-11-18  1:53                   ` Dan Williams [this message]
2016-11-18  9:00                     ` John Garry
2016-11-18  9:00                       ` John Garry
2016-11-18 19:08                       ` Dan Williams
2016-11-21 15:16                         ` John Garry
2016-11-21 15:16                           ` John Garry
2016-11-21 17:13                           ` Dan Williams
2016-11-22 16:56                             ` John Garry
2016-11-22 16:56                               ` John Garry
2016-11-23  1:07                               ` wangyijing
2016-11-23  1:07                                 ` wangyijing

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=CAPcyv4g7_kDAZNZ2ikBRgFsX-hFpcXEV2xg9YS0Ha7PjSBkzVQ@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=jinpu.wang@profitbricks.com \
    --cc=john.garry2@mail.dcu.ie \
    --cc=john.garry@huawei.com \
    --cc=lindar_liu@usish.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=martin.petersen@oracle.com \
    --cc=tj@kernel.org \
    --cc=wangyijing@huawei.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.