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

Date:	Fri, 05 Aug 2011 18:02:50 +0100
From:	"Jan Beulich" <jbeulich@...ell.com>
To:	<matt@...sole-pimps.org>, <johnstul@...ibm.com>
Cc:	<fenghua.yu@...el.com>, <tony.luck@...el.com>,
	<hpa@...ux.intel.com>, <mjg@...hat.com>, <a.zummo@...ertech.it>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86, efi: Don't recursively acquire rtc_lock

>>> Matt Fleming  08/04/11 5:37 PM >>>
>On Thu, 2011-08-04 at 03:22 -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?
>
>Jan wrote the original code that started using the rtc_lock inside the
>EFI bits here, ef68c8f87ed1 ("x86: Serialize EFI time accesses on
>rtc_lock").
>
>Jan?
 
Matthew Garrett already replied to this - it's (on x86) a requirement of the EFI spec.

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/