linux-kernel - Re: [PATCH v2] drm/virtio: Fix memory leak in virtio_gpu_execbuffer

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: <4c3fb9c5-b386-64d7-5d3f-d8633b881222@web.de>
Date:   Mon, 20 Jul 2020 17:29:01 +0200
From:   Markus Elfring <Markus.Elfring@....de>
To:     hexin.op@...edance.com, dri-devel@...ts.freedesktop.org,
        virtualization@...ts.linux-foundation.org,
        linux-media@...r.kernel.org, linaro-mm-sig@...ts.linaro.org
Cc:     Christian König <christian.koenig@....com>,
        Daniel Vetter <daniel@...ll.ch>,
        David Airlie <airlied@...ux.ie>,
        Gerd Hoffmann <kraxel@...hat.com>,
        Sumit Semwal <sumit.semwal@...aro.org>,
        Liu Qi <liuqi.16@...edance.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] drm/virtio: Fix memory leak in
 virtio_gpu_execbuffer_ioctl()

> … To balance the reference
> count initialized when allocating fence, dma_fence_put()
> should not be deleted.

* Would an imperative wording be more appropriate for the change description?

* Is the information “hexin” sufficient for a real name?

Regards,
Markus