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: Thu, 1 Jun 2017 14:02:22 +0000 [thread overview]
Message-ID: <1496325738.3075.1.camel@sandisk.com> (raw)
In-Reply-To: <bd79226b-833c-f53b-f92a-0c4ebffeb1ee@codeaurora.org>
On Thu, 2017-06-01 at 12:28 +0530, Asutosh Das (asd) wrote:
> Please can you check if this is actually a bug and my understanding is
> correct.
Hello Asutosh,
Spinlock recursion is always a bug. With what kernel version did you encounter
this? Was it with a kernel from kernel.org, a distro kernel or an Android kernel?
Have you already tried to reproduce this with kernel debugging enabled? Enabling
CONFIG_DEBUG_SPINLOCK and CONFIG_PROVE_LOCKING should provide more detailed
information.
Bart.
next parent reply other threads:[~2017-06-01 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bd79226b-833c-f53b-f92a-0c4ebffeb1ee@codeaurora.org>
2017-06-01 14:02 ` Bart Van Assche [this message]
2017-06-05 6:46 ` [ufs]: [scsi]: BUG: spinlock recursion on CPU#4 Asutosh Das (asd)
2017-06-05 15:23 ` Bart Van Assche
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=1496325738.3075.1.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 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).