From: Dan Carpenter <dan.carpenter@oracle.com> To: David Airlie <airlied@linux.ie>, Leo Liu <leo.liu@amd.com> Cc: "Jammy Zhou" <Jammy.Zhou@amd.com>, "Christian König" <christian.koenig@amd.com>, "Ken Wang" <Qingqing.Wang@amd.com>, "Alex Deucher" <alexander.deucher@amd.com>, yanyang1 <young.yang@amd.com>, "Marek Olšák" <marek.olsak@amd.com>, dri-devel@lists.freedesktop.org, kernel-janitors@vger.kernel.org Subject: [patch] drm/amdgpu: information leak in amdgpu_info_ioctl() Date: Tue, 28 Jul 2015 15:51:29 +0000 [thread overview] Message-ID: <20150728155129.GC25739@mwanda> (raw) We recently changed the drm_amdgpu_info_device struct so now there is a 4 byte hole at the end. We need to initialize it so we don't disclose secret information from the stack. Fixes: fa92754e9c47 ('drm/amdgpu: add VCE harvesting instance query') Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c index d9de73a..81d60a9 100644 --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c @@ -423,7 +423,7 @@ static int amdgpu_info_ioctl(struct drm_device *dev, void *data, struct drm_file return n ? -EFAULT : 0; } case AMDGPU_INFO_DEV_INFO: { - struct drm_amdgpu_info_device dev_info; + struct drm_amdgpu_info_device dev_info = {}; struct amdgpu_cu_info cu_info; dev_info.device_id = dev->pdev->device;
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com> To: David Airlie <airlied@linux.ie>, Leo Liu <leo.liu@amd.com> Cc: "Jammy Zhou" <Jammy.Zhou@amd.com>, "Christian König" <christian.koenig@amd.com>, "Ken Wang" <Qingqing.Wang@amd.com>, "Alex Deucher" <alexander.deucher@amd.com>, yanyang1 <young.yang@amd.com>, "Marek Olšák" <marek.olsak@amd.com>, dri-devel@lists.freedesktop.org, kernel-janitors@vger.kernel.org Subject: [patch] drm/amdgpu: information leak in amdgpu_info_ioctl() Date: Tue, 28 Jul 2015 18:51:29 +0300 [thread overview] Message-ID: <20150728155129.GC25739@mwanda> (raw) We recently changed the drm_amdgpu_info_device struct so now there is a 4 byte hole at the end. We need to initialize it so we don't disclose secret information from the stack. Fixes: fa92754e9c47 ('drm/amdgpu: add VCE harvesting instance query') Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c index d9de73a..81d60a9 100644 --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c @@ -423,7 +423,7 @@ static int amdgpu_info_ioctl(struct drm_device *dev, void *data, struct drm_file return n ? -EFAULT : 0; } case AMDGPU_INFO_DEV_INFO: { - struct drm_amdgpu_info_device dev_info; + struct drm_amdgpu_info_device dev_info = {}; struct amdgpu_cu_info cu_info; dev_info.device_id = dev->pdev->device;
next reply other threads:[~2015-07-28 15:51 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-28 15:51 Dan Carpenter [this message] 2015-07-28 15:51 ` [patch] drm/amdgpu: information leak in amdgpu_info_ioctl() Dan Carpenter 2015-07-29 1:41 ` Alex Deucher 2015-07-29 1:41 ` Alex Deucher
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=20150728155129.GC25739@mwanda \ --to=dan.carpenter@oracle.com \ --cc=Jammy.Zhou@amd.com \ --cc=Qingqing.Wang@amd.com \ --cc=airlied@linux.ie \ --cc=alexander.deucher@amd.com \ --cc=christian.koenig@amd.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=kernel-janitors@vger.kernel.org \ --cc=leo.liu@amd.com \ --cc=marek.olsak@amd.com \ --cc=young.yang@amd.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.