From: Dan Carpenter <dan.carpenter@oracle.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Jia-Ju Bai <baijiaju1990@163.com>,
devel@driverdev.osuosl.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
scott@matheina.com, airlied@linux.ie, gregkh@linuxfoundation.org,
dri-devel@lists.freedesktop.org, dan.a.cashman@gmail.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
patrik.r.jakobsson@gmail.com, tvboxspy@gmail.com,
linux-pm@vger.kernel.org, forest@alittletooquiet.net,
simon@nikanor.nu, bhelgaas@google.com, golubev.mikhail@gmail.com
Subject: Re: [PATCH] pci: Fix a possible sleep-in-atomic bug in pci_set_power_state
Date: Wed, 11 Oct 2017 16:33:24 +0300 [thread overview]
Message-ID: <20171011133324.b5xnlmj5uhme2ibt@mwanda> (raw)
In-Reply-To: <20171009171517.GL25517@bhelgaas-glaptop.roam.corp.google.com>
On Mon, Oct 09, 2017 at 12:15:17PM -0500, Bjorn Helgaas wrote:
> I assume it's easy to produce an actual failure here? Why haven't we
> seen bug reports about this?
The bug was detected with static analysis. You have to enable a debug
feature in the .config if you want sleeping with spinlock held warnings.
Otherwise you'd have to hit the deadlock and you have to be pretty
unlucky to hit it so these bugs sometimes do go unreported for a long
time.
regards,
dan carpenter
prev parent reply other threads:[~2017-10-11 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 8:16 Jia-Ju Bai
2017-10-09 8:17 ` Greg KH
2017-10-09 8:32 ` Jia-Ju Bai
2017-10-09 17:15 ` Bjorn Helgaas
2017-10-09 17:18 ` Bjorn Helgaas
2017-10-09 18:21 ` Rafael J. Wysocki
2017-10-11 13:33 ` Dan Carpenter [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=20171011133324.b5xnlmj5uhme2ibt@mwanda \
--to=dan.carpenter@oracle.com \
--cc=airlied@linux.ie \
--cc=baijiaju1990@163.com \
--cc=bhelgaas@google.com \
--cc=dan.a.cashman@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=forest@alittletooquiet.net \
--cc=golubev.mikhail@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patrik.r.jakobsson@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=scott@matheina.com \
--cc=simon@nikanor.nu \
--cc=tvboxspy@gmail.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®