linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Colin Ian King <colin.king@canonical.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	kernel-janitors <kernel-janitors@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][next][V2] gpio: sim: Fix dereference of free'd pointer config
Date: Tue, 27 Apr 2021 13:20:26 +0100	[thread overview]
Message-ID: <b80db02b-c940-bc6b-a795-82cd9ff43a6b@canonical.com> (raw)
In-Reply-To: <CAHp75VeFmgOM_APt=pStkU03mP02VgCw0q31bpY7dFnJhKLn8w@mail.gmail.com>

On 27/04/2021 13:11, Andy Shevchenko wrote:
> On Tue, Apr 27, 2021 at 2:49 PM Colin King <colin.king@canonical.com> wrote:
>>
>> From: Colin Ian King <colin.king@canonical.com>
>>
>> The error return of config->id dereferences the kfree'd object config.
>> Fix this by using a temporary variable for the id to avoid this issue.
> 
> Thanks!
> I'm wondering how I missed this... Nevertheless
> 
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> 
>> Addresses-Coverity: ("Read from pointer aftyer free")
> 
> after
> 

Can that be fixed before applying rather me sending a V3?

>> Fixes: a49d14276ac4 ("gpio: sim: allocate IDA numbers earlier")
>> Signed-off-by: Colin Ian King <colin.king@canonical.com>
>> ---
>> V2: Don't make id local to the if statement to improve coding style.
>>     Thanks to Bartosz Golaszewski for this improvement suggestion.
>> ---
>>  drivers/gpio/gpio-sim.c | 8 +++++---
>>  1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpio/gpio-sim.c b/drivers/gpio/gpio-sim.c
>> index 2e2e6399e453..b21541c0b700 100644
>> --- a/drivers/gpio/gpio-sim.c
>> +++ b/drivers/gpio/gpio-sim.c
>> @@ -744,20 +744,22 @@ static struct config_item *
>>  gpio_sim_config_make_item(struct config_group *group, const char *name)
>>  {
>>         struct gpio_sim_chip_config *config;
>> +       int id;
>>
>>         config = kzalloc(sizeof(*config), GFP_KERNEL);
>>         if (!config)
>>                 return ERR_PTR(-ENOMEM);
>>
>> -       config->id = ida_alloc(&gpio_sim_ida, GFP_KERNEL);
>> -       if (config->id < 0) {
>> +       id = ida_alloc(&gpio_sim_ida, GFP_KERNEL);
>> +       if (id < 0) {
>>                 kfree(config);
>> -               return ERR_PTR(config->id);
>> +               return ERR_PTR(id);
>>         }
>>
>>         config_item_init_type_name(&config->item, name,
>>                                    &gpio_sim_chip_config_type);
>>         config->num_lines = 1;
>> +       config->id = id;
>>         mutex_init(&config->lock);
>>
>>         return &config->item;
>> --
>> 2.30.2
>>
> 
> 


  reply	other threads:[~2021-04-27 12:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27 11:49 [PATCH][next][V2] gpio: sim: Fix dereference of free'd pointer config Colin King
2021-04-27 12:11 ` Andy Shevchenko
2021-04-27 12:20   ` Colin Ian King [this message]
2021-04-27 12:57     ` Bartosz Golaszewski

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=b80db02b-c940-bc6b-a795-82cd9ff43a6b@canonical.com \
    --to=colin.king@canonical.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).