linux-kernel - Re: (spurious?) lockdep warning on Xen boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <499B0FBA.4010006@goop.org>
Date:	Tue, 17 Feb 2009 11:27:54 -0800
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Peter Zijlstra <peterz@...radead.org>
CC:	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	the arch/x86 maintainers <x86@...nel.org>,
	Nick Piggin <nickpiggin@...oo.com.au>
Subject: Re: (spurious?) lockdep warning on Xen boot

Peter Zijlstra wrote:
> Right, so you are saying you started out with IRQs enabled, and the
> above local_irq_restore() would simply be the first irq-op to re-enable
> it and goes splat.
>   
Yep.

> In which case your disabled from beginning 'fix' looks like the right
> thing to do.
>   

OK.

>> Or perhaps the second warning is real; in which case, where does the 
>> problem lie? (I guess another case of being bitten by calling 
>> __purge_vmap_area_lazy from interrupt context.)
>>     
>
> Looks like a real problem, and yes your suggestion makes sense.
>   

OK.

Thanks,
    J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/