From: Johannes Thumshirn <morbidrsa@gmail.com>
To: Jose Javier Rodriguez Barbarin <dev-josejavier.rodriguez@duagon.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mcb: Fix incorrect sanity check
Date: Fri, 16 Jan 2026 11:33:02 +0100 [thread overview]
Message-ID: <97cab4b5-ab35-4cbe-a8ee-8ad6ea522159@gmail.com> (raw)
In-Reply-To: <aWoTM8OkirRyeSo-@MNI-190>
On 1/16/26 11:30 AM, Jose Javier Rodriguez Barbarin wrote:
> On Fri, Nov 21, 2025 at 11:54:08AM +0100, Johannes Thumshirn wrote:
>> On 11/21/25 11:33 AM, Jose Javier Rodriguez Barbarin wrote:
>>> On Thu, Nov 20, 2025 at 12:48:45PM +0100, Johannes Thumshirn wrote:
>>>> On 11/20/25 12:37 PM, Jose Javier Rodriguez Barbarin wrote:
>>>>> __mcb_register_driver() makes some sanity checks over mcb_driver
>>>>> to check if .probe and .remove callbacks are set. However, not all
>>>>> mcb device drivers implement .remove callback.
>>>>>
>>>>> Remove .remove check to ensure all mcb device drivers can be loaded.
>>>> The only driver I can see that doesn't implement a .remove method is
>>>> gpio-menz127.c.
>>> Yes. In the past gpio-menz127.c also implemented .remove method, however in
>>>
>>> 3bd13ae04ccc ("gpio: menz127: simplify error path and remove remove()")
>>>
>>> The driver changed, using now devm_* functions so .remove was no longer necessary.
>>>
>>>> Is this safe?
>>>>
>>> From the point of view of mcb bus it should be safe becase I protected the call
>>> of .remove on mcb_remove(), preventing possible crashes when the driver is removed
>>> from the bus.
>>>
>>> I'm afraid I'm lossing something because I cannot understand why these changes are or
>>> not safe. Could you explain me why you understand that these changes are unsafe?
>>
>> Thanks this is the information I was missing from the changelog. I'll change
>> the commit message to:
>>
>> __mcb_register_driver() makes some sanity checks over mcb_driver
>> to check if .probe and .remove callbacks are set. However, since commit
>> 3bd13ae04ccc ("gpio: menz127: simplify error path and remove remove()")
>> removed the .remove callback from menz127-gpio.c, not all mcb device
>> drivers implement .remove callback.
>>
>> Remove .remove check to ensure all mcb device drivers can be loaded.
>>
>> I'll also add
>>
>> Fixes: 3bd13ae04ccc ("gpio: menz127: simplify error path and remove remove()")
>>
>>
>> Thanks,
>>
>> Johannes
>>
> Hi Johannes,
>
> I noticed this patch is not uploaded yet.
>
> I can submit it again changing the commit message as you commented above.
>
> Thank you,
>
> Javier R.
Yes I wanted to forward it to Greg and then I forgot I'm sorry. But I
think it's still in time for v6.20. I'll do so ASAP.
next prev parent reply other threads:[~2026-01-16 10:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 11:37 [PATCH] mcb: Fix incorrect sanity check Jose Javier Rodriguez Barbarin
2025-11-20 11:48 ` Johannes Thumshirn
2025-11-21 10:33 ` Jose Javier Rodriguez Barbarin
2025-11-21 10:54 ` Johannes Thumshirn
2025-11-21 11:02 ` Jose Javier Rodriguez Barbarin
2026-01-16 10:30 ` Jose Javier Rodriguez Barbarin
2026-01-16 10:33 ` Johannes Thumshirn [this message]
2026-01-16 10:37 ` Jose Javier Rodriguez Barbarin
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=97cab4b5-ab35-4cbe-a8ee-8ad6ea522159@gmail.com \
--to=morbidrsa@gmail.com \
--cc=dev-josejavier.rodriguez@duagon.com \
--cc=gregkh@linuxfoundation.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