linux-kernel - Re: [PATCH 2/2] ARM: zynq: drop use of slcr_unlock in zynq_slcr_system

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: <20150319134911.GC23626@jcartwri.amer.corp.natinst.com>
Date:	Thu, 19 Mar 2015 08:49:11 -0500
From:	Josh Cartwright <joshc@...com>
To:	Michal Simek <michal.simek@...inx.com>
Cc:	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	S?ren Brinkmann <soren.brinkmann@...inx.com>
Subject: Re: [PATCH 2/2] ARM: zynq: drop use of slcr_unlock in
 zynq_slcr_system_restart

Ugh.

On Thu, Mar 19, 2015 at 08:33:53AM -0500, Josh Cartwright wrote:
> The SLCR is unconditionally unlocked early on boot in zynq_slcr_init()
> and not unlocked.  As such, it is not necessary to explicitly unlock in

          ^ever re-locked.

Can you fix this up when you apply?

Thanks,
  Josh
--
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/