linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
	kbuild-all@lists.01.org,
	 Linux Memory Management List <linux-mm@kvack.org>,
	Russell King <rmk+kernel@armlinux.org.uk>,
	 Abbott Liu <liuwenliang@huawei.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	 Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [linux-next:master 1570/2472] mm/kasan/init.c:318:9: warning: variable 'pud' set but not used
Date: Fri, 6 Nov 2020 09:53:29 +0100	[thread overview]
Message-ID: <CACRpkdbAXCMTW--BmVs8SQ_u5baaeUob+U57E=4=CrMxWtMO2g@mail.gmail.com> (raw)
In-Reply-To: <CAMj1kXG7uuXmyeDd4Fhfz9HP9APJzgBi_fdgpP4xaL4ObBJ_dA@mail.gmail.com>

On Tue, Nov 3, 2020 at 9:22 AM Ard Biesheuvel <ardb@kernel.org> wrote:

> What about
>
> diff --git a/mm/kasan/init.c b/mm/kasan/init.c
> index fe6be0be1f76..7c3eb1f5a439 100644
> --- a/mm/kasan/init.c
> +++ b/mm/kasan/init.c
> @@ -315,12 +315,10 @@ static void kasan_free_pmd(pmd_t *pmd_start, pud_t *pud)
>
>  static void kasan_free_pud(pud_t *pud_start, p4d_t *p4d)
>  {
> -       pud_t *pud;
>         int i;
>
>         for (i = 0; i < PTRS_PER_PUD; i++) {
> -               pud = pud_start + i;
> -               if (!pud_none(*pud))
> +               if (!pud_none(pud_start[i]))
>                         return;
>         }

Yeah that is way better, also makes the code a lot easier to read.

I sent a patch rewriting all the kasan_free_p??() calls like this.

Yours,
Linus Walleij


      reply	other threads:[~2020-11-06  8:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-01 23:31 [linux-next:master 1570/2472] mm/kasan/init.c:318:9: warning: variable 'pud' set but not used kernel test robot
2020-11-03  0:17 ` Linus Walleij
2020-11-03  8:22   ` Ard Biesheuvel
2020-11-06  8:53     ` Linus Walleij [this message]

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='CACRpkdbAXCMTW--BmVs8SQ_u5baaeUob+U57E=4=CrMxWtMO2g@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=ardb@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=liuwenliang@huawei.com \
    --cc=lkp@intel.com \
    --cc=rmk+kernel@armlinux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).