linux-kernel - Re: [PATCH v2 07/11] drm/ttm: drop VM

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: <20190917114041.6oaukfnsai5rmf54@sirius.home.kraxel.org>
Date:   Tue, 17 Sep 2019 13:40:41 +0200
From:   Gerd Hoffmann <kraxel@...hat.com>
To:     "Koenig, Christian" <Christian.Koenig@....com>
Cc:     "dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
        Thomas Zimmermann <tzimmermann@...e.de>,
        Daniel Vetter <daniel.vetter@...ll.ch>,
        "Huang, Ray" <Ray.Huang@....com>, David Airlie <airlied@...ux.ie>,
        Daniel Vetter <daniel@...ll.ch>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 07/11] drm/ttm: drop VM_DONTDUMP

On Tue, Sep 17, 2019 at 11:22:35AM +0000, Koenig, Christian wrote:
> Am 17.09.19 um 11:24 schrieb Gerd Hoffmann:
> > Not obvious why this is needed.  According to Deniel Vetter this is most
> > likely a historic artefact dating back to the days where drm drivers
> > exposed hardware registers as mmap'able gem objects, to avoid dumping
> > touching those registers.
> 
> Clearly a NAK.
> 
> We still have that and really don't want to try dumping any CPU 
> inaccessible VRAM content even if it is mapped into the address space 
> somewhere.

Thanks for the clarification, I'll drop the patch.

cheers,
  Gerd