From: Heiner Kallweit <hkallweit1@gmail.com>
To: Jean Delvare <jdelvare@suse.de>
Cc: Jean Delvare <jdelvare@suse.com>,
Andi Shyti <andi.shyti@kernel.org>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: i801: fix cleanup code in remove() and error path of probe()
Date: Fri, 1 Sep 2023 14:41:38 +0200 [thread overview]
Message-ID: <dd6c9ddd-da76-ae6d-5903-e945cf950969@gmail.com> (raw)
In-Reply-To: <20230901141929.640fc5d5@endymion.delvare>
On 01.09.2023 14:19, Jean Delvare wrote:
> Hi Heiner,
>
> On Sun, 27 Aug 2023 22:26:05 +0200, Heiner Kallweit wrote:
>> Jean pointed out that the referenced patch resulted in the remove()
>> path not having the reverse order of calls in probe(). I think there's
>> more to be done to ensure proper cleanup.
>> Especially cleanup in the probe() error path has to be extended.
>> Not every step there may be strictly needed, but it's in line with
>> remove() now.
>>
>> Fixes: 9b5bf5878138 ("i2c: i801: Restore INTREN on unload")
>
> I think it also fixes 9424693035a5 ("i2c: i801: Create iTCO device on
> newer Intel PCHs").
>
Right. We should add this, even though this fix won't apply cleanly
on some older kernel versions. I think we'll need separate patches for these
LTS kernel versions.
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>> ---
>> drivers/i2c/busses/i2c-i801.c | 14 ++++++++------
>> 1 file changed, 8 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/i2c/busses/i2c-i801.c b/drivers/i2c/busses/i2c-i801.c
>> index 73ae06432..7a0ccc584 100644
>> --- a/drivers/i2c/busses/i2c-i801.c
>> +++ b/drivers/i2c/busses/i2c-i801.c
>> @@ -1754,6 +1754,9 @@ static int i801_probe(struct pci_dev *dev, const struct pci_device_id *id)
>> "SMBus I801 adapter at %04lx", priv->smba);
>> err = i2c_add_adapter(&priv->adapter);
>> if (err) {
>> + platform_device_unregister(priv->tco_pdev);
>> + outb_p(priv->original_hstcnt, SMBHSTCNT(priv));
>
> Doesn't seem to be needed, as I can't see SMBHSTCNT being written to
> during probe?
>
Right, this is what I was referring to in the commit message when saying
"not every step may be strictly needed". Restoring SMBHSTCNT isn't needed
here, but it makes cleanup in the probe error path the same as in remove
and therefore may improve readability and maintainability.
But I don't insist on it and don't have a strong opinion.
>> + pci_write_config_byte(dev, SMBHSTCFG, priv->original_hstcfg);
>> i801_acpi_remove(priv);
>> return err;
>> }
>> @@ -1779,14 +1782,13 @@ static void i801_remove(struct pci_dev *dev)
>> {
>> struct i801_priv *priv = pci_get_drvdata(dev);
>>
>> - outb_p(priv->original_hstcnt, SMBHSTCNT(priv));
>> - i801_disable_host_notify(priv);
>> i801_del_mux(priv);
>> + i801_disable_host_notify(priv);
>> i2c_del_adapter(&priv->adapter);
>> - i801_acpi_remove(priv);
>> - pci_write_config_byte(dev, SMBHSTCFG, priv->original_hstcfg);
>> -
>> platform_device_unregister(priv->tco_pdev);
>> + outb_p(priv->original_hstcnt, SMBHSTCNT(priv));
>> + pci_write_config_byte(dev, SMBHSTCFG, priv->original_hstcfg);
>> + i801_acpi_remove(priv);
>>
>> /* if acpi_reserved is set then usage_count is incremented already */
>> if (!priv->acpi_reserved)
>> @@ -1803,8 +1805,8 @@ static void i801_shutdown(struct pci_dev *dev)
>> struct i801_priv *priv = pci_get_drvdata(dev);
>>
>> /* Restore config registers to avoid hard hang on some systems */
>> - outb_p(priv->original_hstcnt, SMBHSTCNT(priv));
>> i801_disable_host_notify(priv);
>> + outb_p(priv->original_hstcnt, SMBHSTCNT(priv));
>> pci_write_config_byte(dev, SMBHSTCFG, priv->original_hstcfg);
>> }
>>
>
> Rest looks OK, I'll give it some testing
>
next prev parent reply other threads:[~2023-09-01 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 20:26 [PATCH] i2c: i801: fix cleanup code in remove() and error path of probe() Heiner Kallweit
2023-08-28 22:23 ` Andi Shyti
2023-09-01 12:19 ` Jean Delvare
2023-09-01 12:41 ` Heiner Kallweit [this message]
2023-09-01 17:03 ` Jean Delvare
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=dd6c9ddd-da76-ae6d-5903-e945cf950969@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=jdelvare@suse.com \
--cc=jdelvare@suse.de \
--cc=linux-i2c@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