From: John Ernberg <john.ernberg@actia.se>
To: Shuah Khan <skhan@linuxfoundation.org>,
Michael Grzeschik <grzeschik@puzzle.ch>,
Valentina Manea <valentina.manea.m@gmail.com>,
"Shuah Khan" <shuah@kernel.org>, Hongren Zheng <i@zenithal.me>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: <linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] usbip: stability changes
Date: Tue, 17 Nov 2026 13:33:54 +0100 [thread overview]
Message-ID: <f2bca889-4554-4daa-be61-635fc193a276@actia.se> (raw)
In-Reply-To: <5ffddf60-7549-45a8-8b7d-496967a4e91a@linuxfoundation.org>
Hi Shuah,
On 17/11/2026 00:16, Shuah Khan wrote:
> On 11/13/26 04:34, John Ernberg wrote:
>> Hi Shuah,
>>
>> On 12/11/2026 23:46, Shuah Khan wrote:
>>> On 11/11/26 04:34, Michael Grzeschik wrote:
>>>> While using usbip on kirkwood embedded machine, I came accross
>>>> some stability issues. This series is addressing the reference counting
>>>> on and usage of the event handler itself.
>>>
>>> Tell me more about the stability issues? What doesn't work
>>> without these patches? Do you have reproducers for these
>>> problems?
>>>
>>
>> Since we also had the issue that 2/2 solves: The issue we have is that
>> we see occasional CI failures with ghost USB devices remaining on the
>> client side after our system (server side) had been suspended, even if
>> the device was removed from the server.
>>
>> Applying a patch 2/2 (or our version of it sent earlier) solved the
>> issue.
>
> Hi John,
>
> Can you send Tested-by for the 2/2 - did you also test patch 1/2?
I have not tested patch 1/2 because we have not seen that problem in our
use cases so far, so we do not have a measurement of "good" for that
fix. Michael will have to comment on that one.
Regarding patch 2/2, it seems Michael prefers our version [1].
I can provide a tested-by if you rather want to pick this one.
Best regards // John Ernberg
[1]: https://lore.kernel.org/linux-usb/avToeux2DxhBWGN4@toad.puzzle.ch/
prev parent reply other threads:[~2026-11-17 12:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 11:34 Michael Grzeschik
2026-11-11 11:34 ` [PATCH 1/2] usbip: stub: reference count struct stub_device Michael Grzeschik
2026-11-16 23:15 ` Shuah Khan
2026-11-11 11:34 ` [PATCH 2/2] usbip: identify the event handler with current_work() Michael Grzeschik
2026-11-11 15:35 ` John Ernberg
2026-11-11 21:58 ` Michael Grzeschik
2026-11-12 22:46 ` [PATCH 0/2] usbip: stability changes Shuah Khan
2026-11-13 11:34 ` John Ernberg
2026-11-16 23:16 ` Shuah Khan
2026-11-17 12:33 ` John Ernberg [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=f2bca889-4554-4daa-be61-635fc193a276@actia.se \
--to=john.ernberg@actia.se \
--cc=gregkh@linuxfoundation.org \
--cc=grzeschik@puzzle.ch \
--cc=i@zenithal.me \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=valentina.manea.m@gmail.com \
/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
all inboxes | Powered by JetHome®