linux-kernel - Re: [PATCH v6 0/2] sparc64: Add privileged ADI driver

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] [day] [month] [year] [list]

Message-Id: <20180605.142840.2277897500494503602.davem@davemloft.net>
Date:   Tue, 05 Jun 2018 14:28:40 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     tom.hromatka@...cle.com
Cc:     sparclinux@...r.kernel.org, arnd@...db.de,
        gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
        shuah@...nel.org, linux-kselftest@...r.kernel.org,
        allen.pais@...cle.com, khalid.aziz@...cle.com,
        shannon.nelson@...cle.com, anthony.yznaga@...cle.com
Subject: Re: [PATCH v6 0/2] sparc64: Add privileged ADI driver

From: Tom Hromatka <tom.hromatka@...cle.com>
Date: Thu, 26 Apr 2018 10:54:07 -0600

> ADI is a feature supported on SPARC M7 and newer processors to allow
> hardware to catch rogue accesses to memory. ADI is supported for data
> fetches only and not instruction fetches. An app can enable ADI on its
> data pages, set version tags on them and use versioned addresses to
> access the data pages. Upper bits of the address contain the version
> tag. On M7 processors, upper four bits (bits 63-60) contain the version
> tag. If a rogue app attempts to access ADI enabled data pages, its
> access is blocked and processor generates an exception. Please see
> Documentation/sparc/adi.txt for further details.
> 
> This patchset implements a char driver to read/write ADI versions from
> privileged user space processes.  Intended consumers are makedumpfile
> and crash.

Series applied, but there is one thing I am not happy with.

The hard coded ADI block size.

This value is at least theoretically dynamic, and that is why
it is passed into userspace programs via the ELF AUX vector
at exec() time.

So they should really fetch it from there.