linux-kernel - Re: [PATCH 2/5] arm64: cpufeature: Track unsigned fields

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:	Thu, 19 Nov 2015 10:06:13 +0000
From:	"Suzuki K. Poulose" <Suzuki.Poulose@....com>
To:	AKASHI Takahiro <takahiro.akashi@...aro.org>,
	linux-arm-kernel@...ts.infradead.org
Cc:	catalin.marinas@....com, will.deacon@....com, mark.rutland@....com,
	ard.biesheuvel@...aro.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/5] arm64: cpufeature: Track unsigned fields

On 19/11/15 10:03, Suzuki K. Poulose wrote:
> On 19/11/15 04:57, AKASHI Takahiro wrote:
>> Hi
>>
>>  From my curiosity,
>> can you please clarify your criteria regarding which fields of a register should be signed or unsigned?
>> I guessed that the fields marked with FTR_LOWER_SAFE or FTR_HIGHER_SAFE could be unsigned,

Also, the unsigned values are not restricted to LOWER_SAFE/HIGHER_SAFE, but also applies for
FTR_EXACT, so that we use the appropriate methods to extract them.


Suzuki

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