From: coverity-bot <keescook@chromium.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: "Lijo Lazar" <lijo.lazar@amd.com>,
linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org,
"Jiadong.Zhu" <Jiadong.Zhu@amd.com>,
"Hawking Zhang" <Hawking.Zhang@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"David Airlie" <airlied@gmail.com>,
"Likun Gao" <Likun.Gao@amd.com>,
dri-devel@lists.freedesktop.org, "Tao Zhou" <tao.zhou1@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
yipechai <YiPeng.Chai@amd.com>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
linux-next@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Coverity: gfx_v9_0_init_cp_compute_microcode(): Control flow issues
Date: Thu, 12 Jan 2023 14:24:34 -0800 [thread overview]
Message-ID: <202301121424.5FA0483AB@keescook> (raw)
Hello!
This is an experimental semi-automated report about issues detected by
Coverity from a scan of next-20230111 as part of the linux-next scan project:
https://scan.coverity.com/projects/linux-next-weekly-scan
You're getting this email because you were associated with the identified
lines of code (noted below) that were touched by commits:
Mon Jan 9 17:02:18 2023 -0500
ec787deb2ddf ("drm/amd: Use `amdgpu_ucode_*` helpers for GFX9")
Coverity reported the following:
*** CID 1530548: Control flow issues (DEADCODE)
drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c:1374 in gfx_v9_0_init_cp_compute_microcode()
1368 adev->gfx.mec2_feature_version = adev->gfx.mec_feature_version;
1369 }
1370
1371 gfx_v9_0_check_if_need_gfxoff(adev);
1372 gfx_v9_0_check_fw_write_wait(adev);
1373 if (err) {
vvv CID 1530548: Control flow issues (DEADCODE)
vvv Execution cannot reach this statement: "amdgpu_ucode_release(&adev-...".
1374 amdgpu_ucode_release(&adev->gfx.mec_fw);
1375 amdgpu_ucode_release(&adev->gfx.mec2_fw);
1376 }
1377 return err;
1378 }
1379
If this is a false positive, please let us know so we can mark it as
such, or teach the Coverity rules to be smarter. If not, please make
sure fixes get into linux-next. :) For patches fixing this, please
include these lines (but double-check the "Fixes" first):
Reported-by: coverity-bot <keescook+coverity-bot@chromium.org>
Addresses-Coverity-ID: 1530548 ("Control flow issues")
Fixes: ec787deb2ddf ("drm/amd: Use `amdgpu_ucode_*` helpers for GFX9")
Thanks for your attention!
--
Coverity-bot
reply other threads:[~2023-01-12 22:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202301121424.5FA0483AB@keescook \
--to=keescook@chromium.org \
--cc=Hawking.Zhang@amd.com \
--cc=Jiadong.Zhu@amd.com \
--cc=Likun.Gao@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=YiPeng.Chai@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@embeddedor.com \
--cc=lijo.lazar@amd.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=tao.zhou1@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: 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