From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>,
stable@vger.kernel.org
Cc: kraxel@redhat.com, linux-kernel@vger.kernel.org,
emil.l.velikov@gmail.com, airlied@linux.ie, error27@gmail.com,
gregkh@linuxfoundation.org, darren.kenny@oracle.com,
vegard.nossum@oracle.com
Subject: Re: [PATCH 5.10.y] drm/virtio: Fix error code in virtio_gpu_object_shmem_init()
Date: Sat, 4 Mar 2023 00:32:12 +0300 [thread overview]
Message-ID: <63831405-4a98-9179-e8b8-c34a3c2dd6bb@collabora.com> (raw)
In-Reply-To: <20230302172816.3508816-1-harshit.m.mogalapalli@oracle.com>
On 3/2/23 20:28, Harshit Mogalapalli wrote:
> In virtio_gpu_object_shmem_init() we are passing NULL to PTR_ERR, which
> is returning 0/success.
>
> Fix this by storing error value in 'ret' variable before assigning
> shmem->pages to NULL.
>
> Found using static analysis with Smatch.
>
> Fixes: 64b88afbd92f ("drm/virtio: Correct drm_gem_shmem_get_sg_table() error handling")
> Signed-off-by: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
> ---
> Only compile tested.
>
> Upstream commit b5c9ed70d1a9 ("drm/virtio: Improve DMA API usage for shmem BOs")
> deleted this code, so this patch is not necessary in linux-6.1.y and
> linux-6.2.y.
> ---
> drivers/gpu/drm/virtio/virtgpu_object.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/virtio/virtgpu_object.c b/drivers/gpu/drm/virtio/virtgpu_object.c
> index 168148686001..49fa59e09187 100644
> --- a/drivers/gpu/drm/virtio/virtgpu_object.c
> +++ b/drivers/gpu/drm/virtio/virtgpu_object.c
> @@ -159,8 +159,9 @@ static int virtio_gpu_object_shmem_init(struct virtio_gpu_device *vgdev,
> shmem->pages = drm_gem_shmem_get_sg_table(&bo->base.base);
> if (IS_ERR(shmem->pages)) {
> drm_gem_shmem_unpin(&bo->base.base);
> + ret = PTR_ERR(shmem->pages);
> shmem->pages = NULL;
> - return PTR_ERR(shmem->pages);
> + return ret;
> }
>
> if (use_dma_api) {
Reviewed-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
--
Best regards,
Dmitry
prev parent reply other threads:[~2023-03-03 21:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 17:28 Harshit Mogalapalli
2023-03-03 21:32 ` Dmitry Osipenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=63831405-4a98-9179-e8b8-c34a3c2dd6bb@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=airlied@linux.ie \
--cc=darren.kenny@oracle.com \
--cc=emil.l.velikov@gmail.com \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vegard.nossum@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®