linux-kernel - Re: [PATCH v2] ARM: tegra: switch FUSE clock on before usage

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]

Date:	Fri, 22 Nov 2013 10:35:42 +0900
From:	Alex Courbot <acourbot@...dia.com>
To:	Stephen Warren <swarren@...dotorg.org>,
	Thierry Reding <thierry.reding@...il.com>,
	Peter De Schrijver <pdeschrijver@...dia.com>,
	Prashant Gaikwad <pgaikwad@...dia.com>
CC:	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] ARM: tegra: switch FUSE clock on before usage

On 11/22/2013 05:30 AM, Stephen Warren wrote:
> On 11/20/2013 07:40 PM, Alexandre Courbot wrote:
>> FUSE clock is enabled by most bootloaders, but we cannot expect it to be
>> on in all contexts (e.g. kexec).
>>
>> Ensure the FUSE clock is enabled before any of its registers is touched.
>> Since FUSE is touched very early during system boot (before the clock
>> devices are registered), directly manipulate the clock register bit in
>> case the clock device cannot be acquired.
>
> This looks reasonable to me. I'll apply it soon after -rc1.

Thanks. Be careful as I noticed I misformatted my commit message. The 
part after the "--" will not be stripped by git am as I intended it to 
be. I understood what I did wrong and will hopefully not make that 
mistake again.

Sorry for the inconvenience.
--
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/