From: Guenter Roeck <linux@roeck-us.net>
To: "Nuno Sá" <noname.nuno@gmail.com>
Cc: sashiko@lists.linux.dev,
"Nuno Sá via B4 Relay" <devnull+nuno.sa.analog.com@kernel.org>,
linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v12 2/3] hwmon: ltc4283: Add support for the LTC4283 Swap Controller
Date: Thu, 30 Apr 2026 23:10:09 -0700 [thread overview]
Message-ID: <190bf39b-172d-4852-be86-1d7379d7d4aa@roeck-us.net> (raw)
In-Reply-To: <afOH5xx29LGJ9yKH@nsa>
On 4/30/26 09:50, Nuno Sá wrote:
> On Thu, Apr 30, 2026 at 07:52:55AM -0700, Guenter Roeck wrote:
>> On 4/30/26 03:03, sashiko-bot@kernel.org wrote:
>> ...
>>>> + id = (client->adapter->nr << 10) | client->addr;
>>>> + adev = __devm_auxiliary_device_create(dev, KBUILD_MODNAME, "gpio",
>>>> + &st->gpio_mask, id);
>>>> + if (!adev)
>>>> + return dev_err_probe(dev, -ENODEV, "Failed to add GPIO device\n");
>>>
>>> Can this error path lead to a use-after-free?
>>>
>>> According to the I2C subsystem rules, debugfs entries attached to the
>>> client debugfs directory are only cleaned up during the client device
>>> removal function on driver unbind.
>>>
>>> If __devm_auxiliary_device_create() fails, the probe function aborts and
>>> the devres subsystem frees the st pointer. However, the debugfs files
>>> persist and retain operations that operate on the freed st pointer.
>>>
>>
>> AI taking everything literally :-(. I'll have to reword that guidance again
>> to include the probe error path.
>>
>
> Yeah and it is annoying it always comes up with something that could
> have been said before. Even more annoying some of are legit issues :)
>
Agreed, but I think it it is better that it finds the issues in multiple
rounds than not finding them at all. And I have to say it is very human -
the same happens to me as well when I do code reviews of complex patches.
A major difference is that, unlike me, AI doesn't get tired.
Guenter
next prev parent reply other threads:[~2026-05-01 6:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 8:52 [PATCH v12 0/3] hwmon: Add support for the LTC4283 Hot Swap Controller Nuno Sá via B4 Relay
2026-04-30 8:52 ` [PATCH v12 1/3] dt-bindings: hwmon: Document the LTC4283 " Nuno Sá via B4 Relay
2026-04-30 8:52 ` [PATCH v12 2/3] hwmon: ltc4283: Add support for " Nuno Sá via B4 Relay
2026-04-30 10:03 ` sashiko-bot
2026-04-30 14:52 ` Guenter Roeck
2026-04-30 16:50 ` Nuno Sá
2026-05-01 6:10 ` Guenter Roeck [this message]
2026-05-01 9:07 ` Nuno Sá
2026-04-30 8:52 ` [PATCH v12 3/3] gpio: gpio-ltc4283: " Nuno Sá via B4 Relay
2026-04-30 10:34 ` sashiko-bot
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=190bf39b-172d-4852-be86-1d7379d7d4aa@roeck-us.net \
--to=linux@roeck-us.net \
--cc=devnull+nuno.sa.analog.com@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=noname.nuno@gmail.com \
--cc=sashiko@lists.linux.dev \
/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