From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, emergingsiva@gmail.com
Cc: Sivaraman <sivaramann@ami.com>,
Maciej Rabeda <maciej.rabeda@linux.intel.com>,
Jiaxin Wu <jiaxin.wu@intel.com>, Siyuan Fu <siyuan.fu@intel.com>
Subject: Re: [edk2-devel] [PATCH] NetworkPkg: Addressed static code analyzer issues
Date: Wed, 23 Jun 2021 12:15:22 +0200 [thread overview]
Message-ID: <59d83dd2-1cc8-9cf6-dfaa-3f2e0028ee35@redhat.com> (raw)
In-Reply-To: <b0308d27e6f0ba463decb423e6e84eb695468946.1623985598.git.sivaramann@ami.com>
adding NetworkPkg maintainers, comments below
On 06/18/21 05:30, INDIA\sivaramann wrote:
> Issue on the PxeBcDhcp4CallBack() functions of UEFIPXEBC Driver.
> In this function allowed events are Dhcp4RcvdOffer, Dhcp4SelectOffer,
> Dhcp4SendDiscover, Dhcp4RcvdAck. If any other event comes as input
> it will exit in beginning itself.
Yes.
>
> Later below switch case handling the default case which is not reachable.
> I assume this code is a not reachable code and can be removed
(1) The edk2 coding style recommends adding "default" cases to switch
statements, as far as I recall. I'd keep the default, but add
ASSERT (FALSE);
there.
(2) There is a more confusing style issue with the same switch
statement. Namely, it has a case label for "Dhcp4SendRequest". Control
will never jump to that label, due to the "if" at the top of the
function that you highlight.
Importantly, the *code* starting at the "Dhcp4SendRequest" case label
must not be removed, as the "Dhcp4SendDiscover" logic *falls through* to
it. However, the "Dhcp4SendRequest" case label itself should be removed,
and the comment just above it should be updated.
This dead label seems to originate from historical commit a3bcde70e6dc
("Add NetworkPkg (P.UDK2010.UP3.Network.P1)", 2010-11-01).
(3) The subject line is nearly useless, please name at least
"NetworkPkg/UefiPxeBcDxe".
Thanks
Laszlo
>
> Signed-off-by: Sivaraman <sivaramann@ami.com>
> ---
> NetworkPkg/UefiPxeBcDxe/PxeBcDhcp4.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/NetworkPkg/UefiPxeBcDxe/PxeBcDhcp4.c b/NetworkPkg/UefiPxeBcDxe/PxeBcDhcp4.c
> index fb63cf61a9..c0d8211ea0 100644
> --- a/NetworkPkg/UefiPxeBcDxe/PxeBcDhcp4.c
> +++ b/NetworkPkg/UefiPxeBcDxe/PxeBcDhcp4.c
> @@ -1331,8 +1331,6 @@ PxeBcDhcp4CallBack (
> }
> break;
>
> - default:
> - break;
> }
>
> return Status;
>
next prev parent reply other threads:[~2021-06-23 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 3:30 [PATCH] NetworkPkg: Addressed static code analyzer issues INDIA\sivaramann
2021-06-23 10:15 ` Laszlo Ersek [this message]
2021-06-23 12:03 ` [EXTERNAL] Re: [edk2-devel] " Sivaraman Nainar
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=59d83dd2-1cc8-9cf6-dfaa-3f2e0028ee35@redhat.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