> This isn't necessary (nor desirable). If the API here is that we get called
> from process context for ->open and ->close(), just use the
> spin_lock_irq and spin_unlock_irq variants for these paths (avoiding the need
> to remove the lock acquire in ->open and ->close.
OK. I will update my pa
On Fri, Aug 17, 2012 at 12:42 PM, Seiji Aguchi wrote:
> [Problem]
> Currently, efivars doesn't disable interrupt while taking efivars->lock.
> So, there is a risk to be deadlocking in a write callback of efi_pstore
> if kernel panics in interrupt context while taking efivars->lock.
>
> [Patch D
[Problem]
Currently, efivars doesn't disable interrupt while taking efivars->lock.
So, there is a risk to be deadlocking in a write callback of efi_pstore
if kernel panics in interrupt context while taking efivars->lock.
[Patch Description]
This patch disables an external interruption while ho
3 matches
Mail list logo
