linux-kernel - Re: [git pull] drm/x86 pat regression fix.

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: <CAPM=9tyuS8VN6bEp7-kCzp=iTdGpCkpP+86t1PY7mAkdqtmZYQ@mail.gmail.com>
Date:   Fri, 28 Oct 2016 10:37:37 +1000
From:   Dave Airlie <airlied@...il.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     dri-devel <dri-devel@...ts.freedesktop.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] drm/x86 pat regression fix.

On 26 October 2016 at 16:53, Dave Airlie <airlied@...il.com> wrote:
> Hi Linus,
>
> This is a standalone pull request for the fix for a regression introduced
> in -rc1 by a change to vm_insert_mixed to start using the PAT range tracking
> to validate page protections. With this fix in place, all the VRAM mappings
> for GPU drivers ended up at UC instead of WC.
>
> There are probably better ways to fix this long term, but nothing I'd considered
> for -fixes that wouldn't need more settling in time. So I've just created a new
> arch API that the drivers can reserve all their VRAM aperture ranges as WC.
>
Hey Linus,

was there some problem with this? I've not seen it land yet. I've been
blocking more fixes on this landing.

Dave.