* Andrew Morton <[email protected]> wrote:
> > So, say interrupts were enabled when entering apm_bios_call*(); you now
> > save that in flags, disable interrupts, and enable them again.
> > Upon reaching local_irq_restore(), we'll hit the else branch with irq's
> > enabled and call trace_hardirqs_on(), which goes EEEK!
>
> I'd assumed lockdep was less stupid than that ;) This? Seems a bit
> overdone..
the problem is not lockdep but that the BIOS enables IRQs behind the
back of the kernel. Lockdep needs to be taught about that - if this
happens unconditionally then i'd suggest to insert an unconditional
trace_hardirqs_on() call to after the local_irq_save() that we do prior
calling the BIOS. (that will be a NOP if lockdep is not enabled)
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
