From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"asutoshd@codeaurora.org" <asutoshd@codeaurora.org>
Cc: "linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>
Subject: Re: [ufs]: [scsi]: BUG: spinlock recursion on CPU#4
Date: Mon, 5 Jun 2017 15:23:00 +0000 [thread overview]
Message-ID: <1496676179.2623.3.camel@sandisk.com> (raw)
In-Reply-To: <94899e9e-abd3-5e70-838a-5a4659a9483e@codeaurora.org>
On Mon, 2017-06-05 at 12:16 +0530, Asutosh Das (asd) wrote:
> It's on 4.4 and its an Android kernel.
>
> No - I haven't tried it out yet. I could get some clues from the
> call-stack itself, like I explained before. I can try these configs
> though. While I do that, I'd like to know your thoughts on my analysis.
> Do you think with the current data, it makes sense?
Hello Asutosh,
If your analysis is correct then I think the easiest solution will be to switch
to scsi-mq. The scsi-mq .queue_rq function is called without the host lock held
and hence there is no need to unlock the host lock from inside the queue_rq
function.
Bart.
next prev parent reply other threads:[~2017-06-05 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 6:58 [ufs]: [scsi]: BUG: spinlock recursion on CPU#4 Asutosh Das (asd)
2017-06-01 14:02 ` Bart Van Assche
2017-06-05 6:46 ` Asutosh Das (asd)
2017-06-05 15:23 ` Bart Van Assche [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-01 6:58 Asutosh Das (asd)
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=1496676179.2623.3.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=asutoshd@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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.