linux-kernel - Re: [PATCH RESEND] x86: mm: refer to the intended config STRICT

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: <165730255765.3882379.9761346871433228288.b4-ty@chromium.org>
Date:   Fri,  8 Jul 2022 10:49:20 -0700
From:   Kees Cook <keescook@...omium.org>
To:     lukas.bulwahn@...il.com, dave.hansen@...ux.intel.com
Cc:     Kees Cook <keescook@...omium.org>, kernel-janitors@...r.kernel.org,
        bp@...en8.de, peterz@...radead.org, linux-kernel@...r.kernel.org,
        mingo@...hat.com, tglx@...utronix.de, x86@...nel.org,
        hpa@...or.com, luto@...nel.org
Subject: Re: [PATCH RESEND] x86: mm: refer to the intended config STRICT_DEVMEM in a comment

On Thu, 7 Jul 2022 13:54:42 +0200, Lukas Bulwahn wrote:
> Commit a4866aa81251 ("mm: Tighten x86 /dev/mem with zeroing reads") adds a
> comment to the function devmem_is_allowed() referring to a non-existing
> config STRICT_IOMEM, whereas the comment very likely intended to refer to
> the config STRICT_DEVMEM, as the commit adds some behavior for the config
> STRICT_DEVMEM.
> 
> Most of the initial analysis was actually done by Dave Hansen in the
> email thread below (see Link).
> 
> [...]

Applied to for-next/hardening, thanks!

[1/1] x86: mm: refer to the intended config STRICT_DEVMEM in a comment
      https://git.kernel.org/kees/c/c09327d5673e

-- 
Kees Cook