public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Jean Delvare <jdelvare@suse.com>, Wolfram Sang <wsa@kernel.org>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v3] i2c: i801: Avoid potential double call to gpiod_remove_lookup_table
Date: Tue, 5 Mar 2024 08:06:03 +0100	[thread overview]
Message-ID: <3f49c0df-449b-4c46-b789-ae492957cb5e@gmail.com> (raw)
In-Reply-To: <jn7f4n6nnr24jpp5wo6yz55gm5y3mgwqmwaopxuy5kasvub37x@k7xt7kxjcckd>

On 05.03.2024 00:04, Andi Shyti wrote:
> Hi Heiner,
> 
> On Mon, Mar 04, 2024 at 09:31:06PM +0100, Heiner Kallweit wrote:
>> If registering the platform device fails, the lookup table is
>> removed in the error path. On module removal we would try to
>> remove the lookup table again. Fix this by setting priv->lookup
>> only if registering the platform device was successful.
>> In addition free the memory allocated for the lookup table in
>> the error path.
>>
>> Fixes: d308dfbf62ef ("i2c: mux/i801: Switch to use descriptor passing")
>> Cc: stable@vger.kernel.org
>> Reviewed-by: Andi Shyti <andi.shyti@kernel.org>
>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>> ---
>> v2:
>> - cc stable
>> - free memory allocated for the lookup table
>> v3:
>> - cc'ed Linus
> 
> this patch is a resend...
> 
Right, it's effectively a resend.

>> ---
>>  drivers/i2c/busses/i2c-i801.c | 4 +++-
>>  1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/i2c/busses/i2c-i801.c b/drivers/i2c/busses/i2c-i801.c
>> index 291c609d1..9c624f31c 100644
>> --- a/drivers/i2c/busses/i2c-i801.c
>> +++ b/drivers/i2c/busses/i2c-i801.c
>> @@ -1428,7 +1428,6 @@ static void i801_add_mux(struct i801_priv *priv)
>>  		lookup->table[i] = GPIO_LOOKUP(mux_config->gpio_chip,
>>  					       mux_config->gpios[i], "mux", 0);
>>  	gpiod_add_lookup_table(lookup);
>> -	priv->lookup = lookup;
> 
> if I miss something obvious in my reviews, please let me know...
> I spend most of my time reviewing patches and it happens quite
> often :-)
> 
> Andi
> 
>>  	/*
>>  	 * Register the mux device, we use PLATFORM_DEVID_NONE here
>> @@ -1442,7 +1441,10 @@ static void i801_add_mux(struct i801_priv *priv)
>>  				sizeof(struct i2c_mux_gpio_platform_data));
>>  	if (IS_ERR(priv->mux_pdev)) {
>>  		gpiod_remove_lookup_table(lookup);
>> +		devm_kfree(dev, lookup);
>>  		dev_err(dev, "Failed to register i2c-mux-gpio device\n");
>> +	} else {
>> +		priv->lookup = lookup;
>>  	}
>>  }
>>  
>> -- 
>> 2.44.0
>>


  reply	other threads:[~2024-03-05  7:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 20:31 [PATCH v3] i2c: i801: Avoid potential double call to gpiod_remove_lookup_table Heiner Kallweit
2024-03-04 23:04 ` Andi Shyti
2024-03-05  7:06   ` Heiner Kallweit [this message]
2024-03-05  8:54 ` Linus Walleij
2024-03-05  9:48   ` [SPAM] " Andi Shyti
2024-03-06 11:55 ` Andi Shyti

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=3f49c0df-449b-4c46-b789-ae492957cb5e@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=andi.shyti@kernel.org \
    --cc=jdelvare@suse.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=wsa@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