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

Message-ID: <20110804113655.GA30077@srcf.ucam.org>
Date:	Thu, 4 Aug 2011 12:36:56 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	john stultz <johnstul@...ibm.com>
Cc:	Matt Fleming <matt@...sole-pimps.org>,
	linux-kernel@...r.kernel.org,
	Matt Fleming <matt.fleming@...ux.intel.com>,
	Jan Beulich <JBeulich@...ell.com>,
	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Tony Luck <tony.luck@...el.com>,
	Fenghua Yu <fenghua.yu@...el.com>,
	Alessandro Zummo <a.zummo@...ertech.it>
Subject: Re: [PATCH] x86, efi: Don't recursively acquire rtc_lock

On Thu, Aug 04, 2011 at 03:22:24AM -0700, john stultz wrote:

> Sorry if this should be obvious, but is there a reason your not using
> your own internal lock for serializing the efi bits rather then using
> the rtc_lock?

On x86 systems the EFI clock is almost certainly the AT RTC, so it's 
necessary to serialise accesses between EFI and the traditional clock 
interface.

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