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: <1432731613.2781.13.camel@collabora.co.uk>
Date:	Wed, 27 May 2015 15:00:13 +0200
From:	Sjoerd Simons <sjoerd.simons@...labora.co.uk>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
Cc:	Rob Herring <robh@...nel.org>, Tony Lindgren <tony@...mide.com>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Javier Martinez Canillas <javier.martinez@...labora.co.uk>
Subject: Re: [PATCH 1/2] ARM: cache-l2c: Detect whether it's safe to unlock

Hey Russell,

On Fri, 2015-05-15 at 12:34 +0100, Russell King - ARM Linux wrote:
> On Tue, May 12, 2015 at 09:39:14AM +0200, Sjoerd Simons wrote:
> > To handle that, for caches where special configuration is needed to allow
> > unlocking, check whether this has been setup before unlocking.
> 
> I've come up with a different solution to this, which of course I prefer.
> I'll post the patches later today, thanks.

Did you get round to create/posting those patches? If not, i'm happy to
do a set with your suggested solution as well if you can point me in the
right direction :)

-- 
Sjoerd Simons <sjoerd.simons@...labora.co.uk>
Collabora Ltd.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ