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]

Message-ID: <20110804030441.GA25314@srcf.ucam.org>
Date:	Thu, 4 Aug 2011 04:04:41 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Jan Beulich <jbeulich@...ell.com>
Cc:	matt@...sole-pimps.org, linux-kernel@...r.kernel.org,
	fenghua.yu@...el.com, tony.luck@...el.com, hpa@...ux.intel.com,
	matt.fleming@...ux.intel.com, a.zummo@...ertech.it
Subject: Re: [PATCH] x86, efi: Don't recursively acquire rtc_lock

Well, the rtc_lock is an implementation detail of x86, while we're 
aiming to make the EFI code as general as possible. So I can see the 
argument for moving it to the callers.

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