[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20171011133324.b5xnlmj5uhme2ibt@mwanda>
Date: Wed, 11 Oct 2017 16:33:24 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: Jia-Ju Bai <baijiaju1990@....com>, devel@...verdev.osuosl.org,
"Rafael J. Wysocki" <rjw@...ysocki.net>, scott@...heina.com,
airlied@...ux.ie, gregkh@...uxfoundation.org,
dri-devel@...ts.freedesktop.org, dan.a.cashman@...il.com,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
patrik.r.jakobsson@...il.com, tvboxspy@...il.com,
linux-pm@...r.kernel.org, forest@...ttletooquiet.net,
simon@...anor.nu, bhelgaas@...gle.com, golubev.mikhail@...il.com
Subject: Re: [PATCH] pci: Fix a possible sleep-in-atomic bug in
pci_set_power_state
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
Powered by blists - more mailing lists