From: Oliver Neukum <oneukum@suse.com>
To: Camila Alvarez Inostroza <cam.alvarez.i@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Oliver Neukum <oneukum@suse.com>, USB list <linux-usb@vger.kernel.org>
Subject: Re: Your fix for most_usb.c::hdm_disconnect
Date: Wed, 22 Jan 2025 15:18:28 +0100 [thread overview]
Message-ID: <2fa78a3f-ac17-4b52-9ec2-ed268361d2d5@suse.com> (raw)
In-Reply-To: <8fb2f3dd-99ef-b000-c5f5-44da149786a8@macbook-pro-de-camila.local>
On 22.01.25 14:59, Camila Alvarez Inostroza wrote:
>
>
> On Wed, 22 Jan 2025, Greg Kroah-Hartman wrote:
>
>> On Wed, Jan 22, 2025 at 02:44:59PM +0100, Oliver Neukum wrote:
>>> Hi,
>>>
>>> I am going through syzbot's list of open issues.
>>> It look like like the issue you posted a patch for
>>>
>>> https://lore.kernel.org/all/20240730035745.110637-1-cam.alvarez.i@gmail.com/T/
>>>
>>> is still open. Can something be done? Has the patch been lost?
>>> Is there a remaining issue?
>>
>> The subject line was totally wrong which is why it was probably ignored.
>>
>> Also, are you sure it is right? Grabbing a reference in a disconnect
>> function feels very wrong...
>>
> Yes, I think so as well. I don't think my patch solves the issue at all.
Hi Camila,
thank you for the clarification. Frankly I don't understand the refcounting
logic in this drive. Let's add the author.
Hi Christian,
there is an open issue with the musb driver. May I ask with respect to disconect
handling where the get_device calls, which musb_disconnect() balances with put_device()
are?
Regards
Oliver
prev parent reply other threads:[~2025-01-22 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 13:44 Your fix for most_usb.c::hdm_disconnect Oliver Neukum
2025-01-22 13:52 ` Greg Kroah-Hartman
2025-01-22 13:59 ` Camila Alvarez Inostroza
2025-01-22 14:18 ` Oliver Neukum [this message]
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=2fa78a3f-ac17-4b52-9ec2-ed268361d2d5@suse.com \
--to=oneukum@suse.com \
--cc=cam.alvarez.i@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.