LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ondrej Mosnacek <omosnace@redhat.com>
To: Austin Kim <austindh.kim@gmail.com>
Cc: Paul Moore <paul@paul-moore.com>,
	Stephen Smalley <stephen.smalley.work@gmail.com>,
	Eric Paris <eparis@parisplace.org>,
	SElinux list <selinux@vger.kernel.org>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	kernel-team@lge.com, austin.kim@lge.com
Subject: Re: [PATCH] selinux: remove duplicated initialization of 'i' for clean-up
Date: Tue, 24 Aug 2021 13:27:59 +0200	[thread overview]
Message-ID: <CAFqZXNuOnMpV4RJDej2tp8_2OkZLuxuC9X7jBpKGs00MAQADPQ@mail.gmail.com> (raw)
In-Reply-To: <20210824022247.GA22908@raspberrypi>

Hi Austin,

On Tue, Aug 24, 2021 at 4:23 AM Austin Kim <austindh.kim@gmail.com> wrote:
>
> From: Austin Kim <austin.kim@lge.com>
>
> The local variable 'i' is used to be incremented inside while loop
> within sidtab_convert_tree(). Before while loop, 'i' is set to 0
> inside if/else statement.
>
> Since there is no 'goto' statement within sidtab_convert_tree(),
> it had better initialize 'i' as 0 once before if/else statement.
>
> Signed-off-by: Austin Kim <austin.kim@lge.com>
> ---
>  security/selinux/ss/sidtab.c | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/security/selinux/ss/sidtab.c b/security/selinux/ss/sidtab.c
> index 656d50b09f76..301620de63d3 100644
> --- a/security/selinux/ss/sidtab.c
> +++ b/security/selinux/ss/sidtab.c
> @@ -374,7 +374,7 @@ static int sidtab_convert_tree(union sidtab_entry_inner *edst,
>                                struct sidtab_convert_params *convert)
>  {
>         int rc;
> -       u32 i;
> +       u32 i = 0;
>
>         if (level != 0) {
>                 if (!edst->ptr_inner) {
> @@ -383,7 +383,6 @@ static int sidtab_convert_tree(union sidtab_entry_inner *edst,
>                         if (!edst->ptr_inner)
>                                 return -ENOMEM;
>                 }
> -               i = 0;
>                 while (i < SIDTAB_INNER_ENTRIES && *pos < count) {

I must say I prefer the original version more, because it makes it
clear when you look at the loop that it starts at 0. Once you move the
initialization to the declaration section, readers will have to scan
the code upwards to find it out. As is, it's also less prone to error
if e.g. someone adds another loop before the existing ones and reuses
the variable.

In case anyone is wondering why I didn't make these for loops when I
wrote this code: Since the loop condition a little more than the usual
"for(i = 0; i < n; i++)" pattern, my intention was to emphasize that
this is not a "regular" for loop and that readers should read the loop
carefully to not miss something. But perhaps that's not a good reason
and they would look more natural as for loops. If others think a for
loop would look better here, I'd be OK with a patch that makes these
into for loops instead.

>                         rc = sidtab_convert_tree(&edst->ptr_inner->entries[i],
>                                                  &esrc->ptr_inner->entries[i],
> @@ -400,7 +399,6 @@ static int sidtab_convert_tree(union sidtab_entry_inner *edst,
>                         if (!edst->ptr_leaf)
>                                 return -ENOMEM;
>                 }
> -               i = 0;
>                 while (i < SIDTAB_LEAF_ENTRIES && *pos < count) {
>                         rc = convert->func(&esrc->ptr_leaf->entries[i].context,
>                                            &edst->ptr_leaf->entries[i].context,
> --
> 2.20.1
>

--
Ondrej Mosnacek
Software Engineer, Linux Security - SELinux kernel
Red Hat, Inc.


  reply	other threads:[~2021-08-24 11:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-24  2:22 Austin Kim
2021-08-24 11:27 ` Ondrej Mosnacek [this message]
2021-08-24 13:33   ` Austin Kim
2021-08-24 14:46 ` Paul Moore

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=CAFqZXNuOnMpV4RJDej2tp8_2OkZLuxuC9X7jBpKGs00MAQADPQ@mail.gmail.com \
    --to=omosnace@redhat.com \
    --cc=austin.kim@lge.com \
    --cc=austindh.kim@gmail.com \
    --cc=eparis@parisplace.org \
    --cc=kernel-team@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=selinux@vger.kernel.org \
    --cc=stephen.smalley.work@gmail.com \
    --subject='Re: [PATCH] selinux: remove duplicated initialization of '\''i'\'' for clean-up' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).