On Sun, 2013-03-17 at 04:58 +, Ben Hutchings wrote:
> On Mon, 2013-03-11 at 17:47 -0400, Josh Boyer wrote:
> > Upstream commit 81fa4e581d9283f7992a0d8c534bb141eb840a14
> [...]
>
> This version didn't apply to 3.2.y, but the bug does seem to affect it.
> And efivars is essentially the same in 3
On Mon, 2013-03-11 at 17:47 -0400, Josh Boyer wrote:
> Upstream commit 81fa4e581d9283f7992a0d8c534bb141eb840a14
[...]
This version didn't apply to 3.2.y, but the bug does seem to affect it.
And efivars is essentially the same in 3.2.y and 3.4.y. Does this
backport look right for them?
Ben.
---
Upstream commit 81fa4e581d9283f7992a0d8c534bb141eb840a14
[Problem]
There is a scenario which efi_pstore fails to log messages in a panic case.
- CPUA holds an efi_var->lock in either efivarfs parts
or efi_pstore with interrupt enabled.
- CPUB panics and sends IPI to CPUA in smp_send_stop().