From: Thomas Hellstrom <thellstrom@vmware.com>
To: Alexey Khoroshilov <khoroshilov@ispras.ru>
Cc: David Airlie <airlied@linux.ie>,
Jakob Bornecrant <jakob@vmware.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
ldv-project@linuxtesting.org
Subject: Re: [PATCH] drm/vmwgfx: avoid null pointer dereference at failure paths
Date: Sat, 01 Mar 2014 17:29:45 +0100 [thread overview]
Message-ID: <53120AF9.3070404@vmware.com> (raw)
In-Reply-To: <1393622418-6515-1-git-send-email-khoroshilov@ispras.ru>
On 02/28/2014 10:20 PM, Alexey Khoroshilov wrote:
> vmw_takedown_otable_base() and vmw_mob_unbind() check for
> potential vmw_fifo_reserve() failure and print error message,
> but then immediately dereference NULL pointer.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Alexey Khoroshilov <khoroshilov@ispras.ru>
> ---
> drivers/gpu/drm/vmwgfx/vmwgfx_mob.c | 35 +++++++++++++++++++----------------
> 1 file changed, 19 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_mob.c b/drivers/gpu/drm/vmwgfx/vmwgfx_mob.c
> index d4a5a19cb8c3..04a64b8cd3cd 100644
> --- a/drivers/gpu/drm/vmwgfx/vmwgfx_mob.c
> +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_mob.c
> @@ -188,18 +188,20 @@ static void vmw_takedown_otable_base(struct vmw_private *dev_priv,
>
> bo = otable->page_table->pt_bo;
> cmd = vmw_fifo_reserve(dev_priv, sizeof(*cmd));
> - if (unlikely(cmd == NULL))
> - DRM_ERROR("Failed reserving FIFO space for OTable setup.\n");
> -
> - memset(cmd, 0, sizeof(*cmd));
> - cmd->header.id = SVGA_3D_CMD_SET_OTABLE_BASE;
> - cmd->header.size = sizeof(cmd->body);
> - cmd->body.type = type;
> - cmd->body.baseAddress = 0;
> - cmd->body.sizeInBytes = 0;
> - cmd->body.validSizeInBytes = 0;
> - cmd->body.ptDepth = SVGA3D_MOBFMT_INVALID;
> - vmw_fifo_commit(dev_priv, sizeof(*cmd));
> + if (unlikely(cmd == NULL)) {
> + DRM_ERROR("Failed reserving FIFO space for OTable "
> + "takedown.\n");
> + } else {
> + memset(cmd, 0, sizeof(*cmd));
> + cmd->header.id = SVGA_3D_CMD_SET_OTABLE_BASE;
> + cmd->header.size = sizeof(cmd->body);
> + cmd->body.type = type;
> + cmd->body.baseAddress = 0;
> + cmd->body.sizeInBytes = 0;
> + cmd->body.validSizeInBytes = 0;
> + cmd->body.ptDepth = SVGA3D_MOBFMT_INVALID;
> + vmw_fifo_commit(dev_priv, sizeof(*cmd));
> + }
>
> if (bo) {
> int ret;
> @@ -562,11 +564,12 @@ void vmw_mob_unbind(struct vmw_private *dev_priv,
> if (unlikely(cmd == NULL)) {
> DRM_ERROR("Failed reserving FIFO space for Memory "
> "Object unbinding.\n");
> + } else {
> + cmd->header.id = SVGA_3D_CMD_DESTROY_GB_MOB;
> + cmd->header.size = sizeof(cmd->body);
> + cmd->body.mobid = mob->id;
> + vmw_fifo_commit(dev_priv, sizeof(*cmd));
> }
> - cmd->header.id = SVGA_3D_CMD_DESTROY_GB_MOB;
> - cmd->header.size = sizeof(cmd->body);
> - cmd->body.mobid = mob->id;
> - vmw_fifo_commit(dev_priv, sizeof(*cmd));
> if (bo) {
> vmw_fence_single_bo(bo, NULL);
> ttm_bo_unreserve(bo);
Thanks. I'll queue this for the next vmwgfx-fixes PULL.
/Thomas
prev parent reply other threads:[~2014-03-01 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 21:20 [PATCH] drm/vmwgfx: avoid null pointer dereference at failure paths Alexey Khoroshilov
2014-03-01 16:29 ` Thomas Hellstrom [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=53120AF9.3070404@vmware.com \
--to=thellstrom@vmware.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=jakob@vmware.com \
--cc=khoroshilov@ispras.ru \
--cc=ldv-project@linuxtesting.org \
--cc=linux-kernel@vger.kernel.org \
/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