From: "Sughosh Ganu" <sughosh.ganu@linaro.org>
To: devel@edk2.groups.io, Sami Mujawar <sami.mujawar@arm.com>
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>,
Leif Lindholm <leif@nuviainc.com>,
Matteo.Carlini@arm.com, Ben.Adderson@arm.com, nd <nd@arm.com>
Subject: Re: [edk2-devel] [PATCH v2 1/1] ArmPkg: Fix uninitialised variable in ArmMmuStandaloneMmLib
Date: Fri, 26 Feb 2021 16:28:23 +0530 [thread overview]
Message-ID: <CADg8p940SKQ7aE5UZUfXOr7z-SWfRjRAmbB5q-LxtN+0ro4Z+Q@mail.gmail.com> (raw)
In-Reply-To: <20210225171110.41324-1-sami.mujawar@arm.com>
[-- Attachment #1: Type: text/plain, Size: 1547 bytes --]
On Thu, 25 Feb 2021 at 22:41, Sami Mujawar <sami.mujawar@arm.com> wrote:
> The following patches added support for StandaloneMM using FF-A:
> 9da5ee116a28 ArmPkg: Allow FF-A calls to set memory region's attributes
> 0e43e02b9bd8 ArmPkg: Allow FF-A calls to get memory region's attributes
>
> However, in the error handling logic for the Get/Set Memory attributes,
> the CLANG compiler reports that a status variable could be used without
> initialisation. This issue is a false positive and is not seen with GCC.
>
> The Get/Set Memory attributes operation is atomic and therefore an
> FFA_INTERRUPT or FFA_SUCCESS response is not expected in response
> to FFA_MSG_SEND_DIRECT_REQ. So the remaining cases that could occur
> are:
> - the target sends FFA_MSG_SEND_DIRECT_RESP with a success or
> failure code.
> or
> - FFA_MSG_SEND_DIRECT_REQ transmission failure.
>
> Therefore,
> - reorder the error handling conditions such that it prevents the
> uninitialised variable issue being flagged by CLANG.
> - move the repetitive code to a static helper function and add
> documentation at the appropriate places.
> - fix error handling in functions that invoke GetMemoryPermissions().
>
> Signed-off-by: Sami Mujawar <sami.mujawar@arm.com>
> ---
> The changes can be seen at:
> https://github.com/samimujawar/edk2/tree/1657_stmm_ffa_fix_unused_var_v2
Tested the changes on the StandaloneMm image on the Qemu platform.
Tested-by: Sughosh Ganu <sughosh.ganu@linaro.org>
Reviewed-by: Sughosh Ganu <sughosh.ganu@linaro.org>
-sughosh
[-- Attachment #2: Type: text/html, Size: 2320 bytes --]
next prev parent reply other threads:[~2021-02-26 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 17:11 [PATCH v2 1/1] ArmPkg: Fix uninitialised variable in ArmMmuStandaloneMmLib Sami Mujawar
2021-02-26 10:58 ` Sughosh Ganu [this message]
2021-02-26 18:45 ` [edk2-devel] " Ard Biesheuvel
2021-02-26 22:36 ` Sami Mujawar
2021-02-27 9:40 ` 回复: " gaoliming
2021-02-27 11:11 ` Ard Biesheuvel
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-list 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=CADg8p940SKQ7aE5UZUfXOr7z-SWfRjRAmbB5q-LxtN+0ro4Z+Q@mail.gmail.com \
--to=devel@edk2.groups.io \
/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