Messages in this thread | | | Date | Mon, 25 Aug 2014 10:53:56 +0800 | From | Lan Tianyu <> | Subject | Re: [Bug 3.14.17] inconsistent lock state |
| |
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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |