[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMpxmJXiK+A1AF35OJoKnyYYkJ4VZUgqhzzYOazt-UWaMbCfww@mail.gmail.com>
Date: Thu, 20 Feb 2020 13:45:09 +0100
From: Bartosz Golaszewski <bgolaszewski@...libre.com>
To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc: Bartosz Golaszewski <brgl@...ev.pl>,
Linus Walleij <linus.walleij@...aro.org>,
Khouloud Touil <ktouil@...libre.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
linux-gpio <linux-gpio@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 1/4] nvmem: fix memory leak in error path
czw., 20 lut 2020 o 12:30 Srinivas Kandagatla
<srinivas.kandagatla@...aro.org> napisaĆ(a):
>
>
>
> On 20/02/2020 10:01, Bartosz Golaszewski wrote:
> > - if (IS_ERR(nvmem->wp_gpio))
> > + if (IS_ERR(nvmem->wp_gpio)) {
> > + ida_simple_remove(&nvmem_ida, nvmem->id);
> > + kfree(nvmem);
> > return ERR_CAST(nvmem->wp_gpio);
> You freed nvmem just before this statement, how can nvmem->wp_gpio be
> still be valid?
>
> Are you able to test this changes at your end?
> Or
> these are just compile tested?
>
Sorry this was rushed, I will have access to the HW for testing tomorrow.
Bartosz
Powered by blists - more mailing lists