From: Richard Yao <ryao@gentoo.org>
To: Joe Lawrence <joe.lawrence@stratus.com>,
"Reddy, Sreekanth" <Sreekanth.Reddy@lsi.com>
Cc: "prometheanfire@gentoo.org" <prometheanfire@gentoo.org>,
"Nandigama, Nagalakshmi" <Nagalakshmi.Nandigama@lsi.com>,
Support <support@lsi.com>,
DL-MPT Fusion Linux <DL-MPTFusionLinux@lsi.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"JBottomley@parallels.com" <JBottomley@parallels.com>,
"kernel@gentoo.org" <kernel@gentoo.org>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: mpt2sas driver barfs when force removing a drive on 3.13.1
Date: Wed, 12 Feb 2014 12:41:43 -0500 [thread overview]
Message-ID: <52FBB257.10304@gentoo.org> (raw)
In-Reply-To: <20140212114308.4f57a8b5@jlaw-desktop.mno.stratus.com>
[-- Attachment #1: Type: text/plain, Size: 2896 bytes --]
You should use `git send-email` to send the patch to all of the people
listed by get_maintainer.pl:
richard@desktop ~/devel/linux $ scripts/get_maintainer.pl --file
drivers/scsi/scsi_transport_sas.c
"James E.J. Bottomley" <JBottomley@parallels.com> (maintainer:SCSI
SUBSYSTEM)
linux-scsi@vger.kernel.org (open list:SCSI SUBSYSTEM)
linux-kernel@vger.kernel.org (open list)
If I see that James E.J. Bottomley is already on CC for this discussion,
but my recent (and first) experience submitting a patch for another
subsystem was that they are ignored unless this strict procedure is
followed.
If the maintainer does not respond within a month after doing this, I
suggest informing Linus Torvalds via email that the subsystem maintainer
is non-responsive.
On 02/12/2014 11:43 AM, Joe Lawrence wrote:
> Hi Sreekanth,
>
> There hasn't been much recent activity in
> drivers/scsi/scsi_transport_sas.c, so I wasn't sure who could best
> review the patch.
>
> Dan Williams added sas_rphy_unlink() back in 2011, perhaps he can
> remember why sas_bsg_remove wasn't performed there?
>
> Regards,
>
> -- Joe
>
>
> On Wed, 12 Feb 2014 11:43:58 +0000
> "Reddy, Sreekanth" <Sreekanth.Reddy@lsi.com> wrote:
>
>> Hi Joe,
>>
>> May I known the status of this patch having subject
>> "[PATCH] scsi_transport_sas: move bsg destructor into sas_rphy_remove".
>>
>> I need the status of this patch as I am also observing the same WARNING call trace on latest 3.14.0-rc2+ kernel whenever we unload the mpt2sas/mpt3sas driver or whenever we unplug the drive attached to the HBA.
>> But after applying yours patch, these WARNING call trace is not observed.
>>
>> Regards,
>> Sreekanth
>>
>>> -----Original Message-----
>>> From: Joe Lawrence [mailto:joe.lawrence@stratus.com]
>>> Sent: Monday, February 03, 2014 7:54 PM
>>> To: prometheanfire@gentoo.org
>>> Cc: Nandigama, Nagalakshmi; Reddy, Sreekanth; Support; DL-MPT Fusion
>>> Linux; linux-scsi@vger.kernel.org; JBottomley@parallels.com; linux-
>>> kernel@vger.kernel.org; kernel@gentoo.org
>>> Subject: Re: mpt2sas driver barfs when force removing a drive on 3.13.1
>>>
>>> On Fri, 31 Jan 2014 20:49:39 -0600
>>> Matthew Thode <prometheanfire@gentoo.org> wrote:
>>>
>>>> I decided to pull a drive while it was in use out of laziness (it was
>>>> open via luks, but not in actual use). Got a fun trace as a result.
>>>> Just thought you'd like to know :D
>>>>
>>>
>>> Hi Matthew,
>>>
>>> The first trace looks a lot like what I see on mpt2sas driver removal [1]. I
>>> posted a suggested fix back in Dec [2], which you might try, however it is not
>>> reviewed at this point.
>>>
>>> [1] http://thread.gmane.org/gmane.linux.scsi/86237
>>> [2] https://github.com/joe-
>>> lawrence/linux/compare/scsi_transport_sas_sysfs_warning.patch
>>>
>>> Regards,
>>>
>>> -- Joe
>>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2014-02-12 17:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 2:49 mpt2sas driver barfs when force removing a drive on 3.13.1 Matthew Thode
2014-02-03 14:24 ` Joe Lawrence
2014-02-12 11:43 ` Reddy, Sreekanth
2014-02-12 16:43 ` Joe Lawrence
2014-02-12 17:41 ` Richard Yao [this message]
2014-02-12 19:25 ` Dan Williams
2014-02-12 19:41 ` Richard Yao
2014-02-12 19:46 ` Matthew Thode
2014-02-14 5:48 ` Matthew Thode
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=52FBB257.10304@gentoo.org \
--to=ryao@gentoo.org \
--cc=DL-MPTFusionLinux@lsi.com \
--cc=JBottomley@parallels.com \
--cc=Nagalakshmi.Nandigama@lsi.com \
--cc=Sreekanth.Reddy@lsi.com \
--cc=dan.j.williams@intel.com \
--cc=joe.lawrence@stratus.com \
--cc=kernel@gentoo.org \
--cc=linux-scsi@vger.kernel.org \
--cc=prometheanfire@gentoo.org \
--cc=support@lsi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox