linux-kernel - Re: [PATCH 4.20 004/352] drm/vgem: Fix vgem

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

Date:   Thu, 14 Feb 2019 15:19:47 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Emil Velikov <emil.velikov@...labora.com>
Cc:     linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        Daniel Vetter <daniel.vetter@...ll.ch>,
        Deepak Sharma <deepak.sharma@....com>,
        Sean Paul <seanpaul@...omium.org>,
        Sasha Levin <sashal@...nel.org>
Subject: Re: [PATCH 4.20 004/352] drm/vgem: Fix vgem_init to get drm device
 available.

On Thu, Feb 14, 2019 at 01:58:02PM +0000, Emil Velikov wrote:
> Hi Greg,
> 
> On 2019/02/11, Greg Kroah-Hartman wrote:
> > 4.20-stable review patch.  If anyone has any objections, please let me know.
> > 
> > ------------------
> > 
> > [ Upstream commit d5c04dff24870ef07ce6453a3f4e1ffd9cf88d27 ]
> > 
> > Modify vgem_init to take platform dev as parent in drm_dev_init.
> > This will make drm device available at "/sys/devices/platform/vgem"
> > in x86 chromebook.
> > 
> > v2: rebase, address checkpatch typo and line over 80 characters
> > 
> > Cc: Daniel Vetter <daniel.vetter@...ll.ch>
> > Signed-off-by: Deepak Sharma <deepak.sharma@....com>
> > Reviewed-by: Sean Paul <seanpaul@...omium.org>
> > Signed-off-by: Emil Velikov <emil.velikov@...labora.com>
> > Reviewed-by: Daniel Vetter <daniel.vetter@...ll.ch>
> > Link: https://patchwork.freedesktop.org/patch/msgid/20181023163550.15211-1-emil.l.velikov@gmail.com
> > Signed-off-by: Sasha Levin <sashal@...nel.org>
> 
> Zero objections to picking this for stable, although I'm curious what
> flagged this commit as stable material.
> 
> Especially since it's closer to a feature than a bug-fix.
> 
> Can you share some light? Perhaps a link to a thread/document since I
> would imagine you've been asked before.

Sasha has a presentation all about how this gets picked up, but I can't
find the link right now.  Sasha?