linux-kernel - Re: [PATCH] x86, efi: Don't recursively acquire rtc

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 16 Aug 2011 07:22:06 +0100
From:	"Jan Beulich" <JBeulich@...ell.com>
To:	"Matt Fleming" <matt@...sole-pimps.org>
Cc:	"Jeremy Fitzhardinge" <jeremy.fitzhardinge@...rix.com>,
	"Ingo Molnar" <mingo@...e.hu>,
	"Thomas Gleixner" <tglx@...utronix.de>, <hpa@...ux.intel.com>,
	"Avi Kivity" <avi@...hat.com>, <mjg@...hat.com>,
	"MarceloTosatti" <mtosatti@...hat.com>,
	"johnstultz" <johnstul@...ibm.com>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86, efi: Don't recursively acquire rtc_lock

>>> On 15.08.11 at 20:18, Matt Fleming <matt@...sole-pimps.org> wrote:
> On Wed, 2011-08-10 at 14:12 +0100, Jan Beulich wrote:
>> Bottom line - the fix here is needed for 32-bit booting only (and
>> hence isn't - afaic - as critical as I first thought). But the adjustment
>> I'm holding is a necessary one (and I don't even understand why,
>> when 32- and 64-bit EFI code got merged, this was left 32-bit only),
>> and the NX consolidation change needs to be fixed too (basically as
>> a prerequisite).
> 
> But the rtc-lock patch is independent and can be merged on its own,
> right? Sure the other issues need fixing but there's no sense in holding
> up the rtc-lock patch, since with it applied my machine actually boots.

Oh, yes, absolutely - I'm actually waiting for this one to get applied so
that the enabling of the use of the EFI RTC routines on x86-64 won't
cause the same problem there.

Jan

--
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/