From: Christian Borntraeger <borntraeger@de.ibm.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
Steffen Maier <maier@linux.vnet.ibm.com>
Cc: "Dan Carpenter" <dan.carpenter@oracle.com>,
linux-scsi@vger.kernel.org,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin Schwidefsky" <schwidefsky@de.ibm.com>,
"Heiko Carstens" <heiko.carstens@de.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org,
"Hendrik Brückner" <brueckner@linux.vnet.ibm.com>,
"Gerald Schaefer" <gerald.schaefer@de.ibm.com>
Subject: Re: [patch] zfcp: spin_lock_irqsave() is not nestable
Date: Tue, 25 Oct 2016 09:28:29 +0200 [thread overview]
Message-ID: <e926cd4a-ba76-36f0-9d1c-d039d9ca5d11@de.ibm.com> (raw)
In-Reply-To: <63c024b9-8662-e521-62e0-e0ebe980b217@de.ibm.com>
On 10/24/2016 10:18 AM, Christian Borntraeger wrote:
> On 10/14/2016 10:21 PM, Martin K. Petersen wrote:
>>>>>>> "Steffen" == Steffen Maier <maier@linux.vnet.ibm.com> writes:
>>
>> Steffen> could you please queue this as fix for one of my patches that
>> Steffen> went into the 4.9 merge window, so for 4.9-rc I guess?
>>
>> Applied to 4.9/scsi-fixes.
>>
>
> FWIW, I do see rcu stall errors with 4.9-rc1 from time to time, so I assume
> that this fix is not only theoretical but fixes a real life issue.
Yes, with that patch the rcu stalls are gone, I assume its already on a branch
that does not rebase, otherwise feel free to add
Tested-by: Christian Borntraeger <borntraeger@de.ibm.com>
prev parent reply other threads:[~2016-10-25 7:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 8:53 Dan Carpenter
2016-10-13 10:49 ` Steffen Maier
2016-10-13 11:27 ` Dan Carpenter
2016-10-14 20:21 ` Martin K. Petersen
2016-10-24 8:18 ` Christian Borntraeger
2016-10-25 7:28 ` Christian Borntraeger [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=e926cd4a-ba76-36f0-9d1c-d039d9ca5d11@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=brueckner@linux.vnet.ibm.com \
--cc=dan.carpenter@oracle.com \
--cc=gerald.schaefer@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=maier@linux.vnet.ibm.com \
--cc=martin.petersen@oracle.com \
--cc=schwidefsky@de.ibm.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
all inboxes | Powered by JetHome®