From: Lan Tianyu <tianyu.lan@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Knut Petersen <Knut_Petersen@t-online.de>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Thomas Renninger <trenn@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 3.14.17] inconsistent lock state
Date: Mon, 25 Aug 2014 10:53:56 +0800 [thread overview]
Message-ID: <53FAA544.4030401@intel.com> (raw)
In-Reply-To: <CA+55aFwZP1gyf=mvTrKjWwj6YE6=5y1+aZdmsNMHUp6d3dckXw@mail.gmail.com>
On 2014年08月25日 01:50, Linus Torvalds wrote:
> Rafael? Lan Tianyu? This is not some minor locking bug. This is a
> *major* mistake unless I misread something.
>
Hi Linus:
Sorry about this. We are resolving the issue in the other bug
report(https://lkml.org/lkml/2014/8/21/606) and I have proposed a fix
patch(http://marc.info/?l=linux-acpi&m=140869309231199&w=2).
It's my fault. ACPI button notify callback will be called in the
interrupt context when the button device is enumerated from ACPI FADT
table(So called fixed button device). The ACPI button device also can be
enumerated from ACPI namespace and its callback will be run in the
process context just like other ACPI devices' notify callbacks. These
two kind of butt devices uses the same callback. Originally, I assumed
all ACPI notify callbacks were run in the process context and didn't
check whether netlink routine can use in the interrupt context or not.
Sorry again.
> Linus
>
--
Best regards
Tianyu Lan
next prev parent reply other threads:[~2014-08-25 2:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53F9CC77.70009@t-online.de>
2014-08-24 17:50 ` [Bug 3.14.17] inconsistent lock state Linus Torvalds
2014-08-24 18:13 ` Arkadiusz Miskiewicz
2014-08-24 18:49 ` Linus Torvalds
2014-08-24 19:04 ` David Miller
2014-08-25 2:53 ` Lan Tianyu [this message]
2014-08-25 3:13 ` Linus Torvalds
2014-08-25 3:43 ` Lan Tianyu
[not found] ` <53FAE383.6050308@t-online.de>
2014-08-25 16:36 ` Linus Torvalds
[not found] ` <53FBA94E.2080405@t-online.de>
[not found] ` <53FBBC26.2030501@oracle.com>
2014-08-26 4:10 ` [REGRESSION] pci: power off broken by commit 4fc9bbf98 / stable 2ab0ff9b Bjorn Helgaas
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=53FAA544.4030401@intel.com \
--to=tianyu.lan@intel.com \
--cc=Knut_Petersen@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=trenn@suse.de \
/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