linux-kernel - Re: [PATCH] x86/dmi: Switch dmi_remap to ioremap

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]

Date:   Thu, 9 Mar 2017 10:14:02 -0800
From:   Andy Lutomirski <luto@...capital.net>
To:     Arjan van de Ven <arjan@...ux.intel.com>
Cc:     Julian Brost <julian.brost@....de>,
        Andy Lutomirski <luto@...nel.org>,
        Jean Delvare <jdelvare@...e.de>, X86 ML <x86@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Borislav Petkov <bp@...en8.de>,
        Brian Gerst <brgerst@...il.com>,
        Denys Vlasenko <dvlasenk@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        "Luis R. Rodriguez" <mcgrof@...e.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Toshi Kani <toshi.kani@...com>, Ingo Molnar <mingo@...nel.org>,
        problems@....cs.fau.de
Subject: Re: [PATCH] x86/dmi: Switch dmi_remap to ioremap_cache

On Thu, Mar 9, 2017 at 9:51 AM, Arjan van de Ven <arjan@...ux.intel.com> wrote:
> On 3/9/2017 9:48 AM, Julian Brost wrote:
>
>> I'm note entirely sure whether it's actually the kernel or HP to blame,
>> but for now, hp-health is completely broken on 4.9 (probably on
>> everything starting from 4.6), so this patch should be reviewed again.
>
>
> it looks like another kernel driver is doing a conflicting mapping.
> do these HP tools come with their own kernel drivers or are those in the
> upstream kernel nowadays?
>

I assume that the kernel DMI driver itself is now a conflicting
mapping.  I wonder if it could register some kind of resource so that
/dev/mem knows to just map it writeback.

On the other hand, the right answer is to use /sys/firmware/dmi.  I'm
not sure the kernel ABI stability guarantee applies to /dev/mem.

--Andy