From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
<linux-scsi@vger.kernel.org>, Omar Sandoval <osandov@osandov.com>,
"Hannes Reinecke" <hare@suse.com>,
Sagi Grimberg <sagi@grimberg.me>, Christoph Hellwig <hch@lst.de>,
Sathya Prakash <sathya.prakash@broadcom.com>,
Chaitra P B <chaitra.basappa@broadcom.com>,
Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com>,
Sreekanth Reddy <Sreekanth.Reddy@broadcom.com>,
"# v4 . 10+" <stable@vger.kernel.org>
Subject: Re: [PATCH] mpt3sas: Avoid sleeping in interrupt context
Date: Wed, 01 Mar 2017 21:53:42 -0500 [thread overview]
Message-ID: <yq1lgsoqthl.fsf@oracle.com> (raw)
In-Reply-To: <20170301170036.11540-1-bart.vanassche@sandisk.com> (Bart Van Assche's message of "Wed, 1 Mar 2017 09:00:36 -0800")
>>>>> "Bart" == Bart Van Assche <bart.vanassche@sandisk.com> writes:
Bart> Commit 669f044170d8 ("scsi: srp_transport: Move queuecommand()
Bart> wait code to SCSI core") can make scsi_internal_device_block()
Bart> sleep. However, the mpt3sas driver can call this function from an
Bart> interrupt handler. Hence add a second argument to
Bart> scsi_internal_device_block() that restores the old behavior of
Bart> this function for the mpt3sas handler.
Applied to 4.11/scsi-fixes.
Thanks, Bart!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2017-03-02 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 17:00 [PATCH] mpt3sas: Avoid sleeping in interrupt context Bart Van Assche
2017-03-01 17:04 ` Omar Sandoval
2017-03-01 17:09 ` Bart Van Assche
2017-03-01 17:28 ` Omar Sandoval
2017-03-01 17:32 ` Bart Van Assche
2017-03-02 2:53 ` Martin K. Petersen [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=yq1lgsoqthl.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Sreekanth.Reddy@broadcom.com \
--cc=bart.vanassche@sandisk.com \
--cc=chaitra.basappa@broadcom.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
--cc=osandov@osandov.com \
--cc=sagi@grimberg.me \
--cc=sathya.prakash@broadcom.com \
--cc=stable@vger.kernel.org \
--cc=suganath-prabu.subramani@broadcom.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;
as well as URLs for NNTP newsgroup(s).