From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Chen, Guchun" <Guchun.Chen@amd.com>
Cc: "kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
"lkp@intel.com" <lkp@intel.com>,
"kbuild@lists.01.org" <kbuild@lists.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>
Subject: Re: [kbuild] drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c:1433 amdgpu_discovery_get_vcn_info() error: buffer overflow 'adev->vcn.vcn_codec_disable_mask' 2 <= 3
Date: Fri, 27 May 2022 11:12:59 +0300 [thread overview]
Message-ID: <20220527081259.GN2168@kadam> (raw)
In-Reply-To: <DM5PR12MB246988B514599DF631847549F1D89@DM5PR12MB2469.namprd12.prod.outlook.com>
On Fri, May 27, 2022 at 07:56:48AM +0000, Chen, Guchun wrote:
> A patch was available already to protect against such scenario.
>
> https://patchwork.freedesktop.org/patch/486289/ , "drm/amdgpu/discovery: validate VCN and SDMA instances"
>
What? That's an unrelated patch and it has already been applied so I
took it into consideration when doing my analysis.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: kbuild@lists.01.org
Subject: Re: drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c:1433 amdgpu_discovery_get_vcn_info() error: buffer overflow 'adev->vcn.vcn_codec_disable_mask' 2 <= 3
Date: Fri, 27 May 2022 11:12:59 +0300 [thread overview]
Message-ID: <20220527081259.GN2168@kadam> (raw)
In-Reply-To: <DM5PR12MB246988B514599DF631847549F1D89@DM5PR12MB2469.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
On Fri, May 27, 2022 at 07:56:48AM +0000, Chen, Guchun wrote:
> A patch was available already to protect against such scenario.
>
> https://patchwork.freedesktop.org/patch/486289/ , "drm/amdgpu/discovery: validate VCN and SDMA instances"
>
What? That's an unrelated patch and it has already been applied so I
took it into consideration when doing my analysis.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: kbuild-all@lists.01.org
Subject: Re: [kbuild] drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c:1433 amdgpu_discovery_get_vcn_info() error: buffer overflow 'adev->vcn.vcn_codec_disable_mask' 2 <= 3
Date: Fri, 27 May 2022 11:12:59 +0300 [thread overview]
Message-ID: <20220527081259.GN2168@kadam> (raw)
In-Reply-To: <DM5PR12MB246988B514599DF631847549F1D89@DM5PR12MB2469.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
On Fri, May 27, 2022 at 07:56:48AM +0000, Chen, Guchun wrote:
> A patch was available already to protect against such scenario.
>
> https://patchwork.freedesktop.org/patch/486289/ , "drm/amdgpu/discovery: validate VCN and SDMA instances"
>
What? That's an unrelated patch and it has already been applied so I
took it into consideration when doing my analysis.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Chen, Guchun" <Guchun.Chen@amd.com>
Cc: "kbuild@lists.01.org" <kbuild@lists.01.org>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
"kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
"lkp@intel.com" <lkp@intel.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [kbuild] drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c:1433 amdgpu_discovery_get_vcn_info() error: buffer overflow 'adev->vcn.vcn_codec_disable_mask' 2 <= 3
Date: Fri, 27 May 2022 11:12:59 +0300 [thread overview]
Message-ID: <20220527081259.GN2168@kadam> (raw)
In-Reply-To: <DM5PR12MB246988B514599DF631847549F1D89@DM5PR12MB2469.namprd12.prod.outlook.com>
On Fri, May 27, 2022 at 07:56:48AM +0000, Chen, Guchun wrote:
> A patch was available already to protect against such scenario.
>
> https://patchwork.freedesktop.org/patch/486289/ , "drm/amdgpu/discovery: validate VCN and SDMA instances"
>
What? That's an unrelated patch and it has already been applied so I
took it into consideration when doing my analysis.
regards,
dan carpenter
next prev parent reply other threads:[~2022-05-27 8:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 7:14 drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c:1433 amdgpu_discovery_get_vcn_info() error: buffer overflow 'adev->vcn.vcn_codec_disable_mask' 2 <= 3 kernel test robot
2022-05-27 7:46 ` [kbuild] " Dan Carpenter
2022-05-27 7:46 ` Dan Carpenter
2022-05-27 7:46 ` Dan Carpenter
2022-05-27 7:56 ` Chen, Guchun
2022-05-27 8:12 ` Dan Carpenter [this message]
2022-05-27 8:12 ` Dan Carpenter
2022-05-27 8:12 ` Dan Carpenter
2022-05-27 8:12 ` Dan Carpenter
2022-05-27 7:56 ` [kbuild] " Chen, Guchun
2022-06-01 18:43 ` Alex Deucher
2022-06-01 18:43 ` Alex Deucher
2022-06-01 18:43 ` Alex Deucher
2022-06-02 6:26 ` Ernst Sjöstrand
2022-06-02 6:26 ` Ernst Sjöstrand
2022-06-02 11:50 ` Dan Carpenter
2022-06-02 11:50 ` Dan Carpenter
2022-06-02 11:50 ` Dan Carpenter
2022-06-02 11:50 ` Dan Carpenter
2022-06-02 14:24 ` [kbuild] " Alex Deucher
2022-06-02 14:24 ` Alex Deucher
2022-06-02 15:33 ` Dan Carpenter
2022-06-02 15:33 ` Dan Carpenter
2022-06-02 15:33 ` Dan Carpenter
2022-06-02 15:44 ` [kbuild] " Alex Deucher
2022-06-02 15:44 ` 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=20220527081259.GN2168@kadam \
--to=dan.carpenter@oracle.com \
--cc=Alexander.Deucher@amd.com \
--cc=Guchun.Chen@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=kbuild-all@lists.01.org \
--cc=kbuild@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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 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.