linux-kernel - Re: [PATCH, resend] x86: enable rtc-efi

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: <20120515134017.GA26656@srcf.ucam.org>
Date:	Tue, 15 May 2012 14:40:17 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Jan Beulich <JBeulich@...e.com>
Cc:	dannf@...nf.org, mingo@...e.hu, tglx@...utronix.de,
	matt.fleming@...ux.intel.com, linux-kernel@...r.kernel.org,
	hpa@...or.com
Subject: Re: [PATCH, resend] x86: enable rtc-efi

On Tue, May 15, 2012 at 02:36:18PM +0100, Jan Beulich wrote:
> >>> On 15.05.12 at 15:26, Matthew Garrett <mjg59@...f.ucam.org> wrote:
> > On Tue, May 15, 2012 at 02:22:53PM +0100, Jan Beulich wrote:
> > 
> >> I don't think so - the two drivers could end up manipulating the
> >> same piece of hardware, without synchronization. rtc-cmos
> >> really should bail when loaded on an EFI-enabled system.
> > 
> > That's why we're taking the rtc lock.
> 
> Which is completely bogus imo (i.e. it should be a goal to remove
> this).

Sure, once we've fixed the EFI clock and made sure that there's no 
lingering accesses to the old nvram.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/