From: Shuah Khan <skhan@linuxfoundation.org>
To: "Sosthène Guédon" <sosthene@nitrokey.com>,
"Valentina Manea" <valentina.manea.m@gmail.com>,
"Shuah Khan" <shuah@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Robin Krahl <robin@nitrokey.com>, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: kernel BUG at mm/usercopy.c when using usbip
Date: Thu, 12 Jan 2023 08:40:26 -0700 [thread overview]
Message-ID: <db42f90b-dec3-1e2b-c973-b4dc76cd4830@linuxfoundation.org> (raw)
In-Reply-To: <4c9a5640-9ebf-db87-fcb0-b076b615e4e4@linuxfoundation.org>
On 1/12/23 08:13, Shuah Khan wrote:
> On 1/12/23 01:40, Sosthène Guédon wrote:
>> Hi!
>>
>> I have stumbled upon a bug that is triggered reliably by using usbip.
>>
>> We are using usbip to test our firmware. usbip attach works, but once `opgpcard-tools` interacts with the firmware through pcscd, a kernel bug happens.
>> Then usbip stops working, and `lsusb` as well as other tools interacting with usb devices hang.
>> The symptoms are similar to https://bugzilla.kernel.org/show_bug.cgi?id=215487 but the kernel bug is not the same (see attached dmesg logs).
>>
>> The bug can be reproduced on arch (Linux archlinux 6.1.4-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 07 Jan 2023 15:10:07 +0000 x86_64 GNU/Linux
>> ) and debian (Linux nitropc 5.10.0-19-amd64 #1 SMP Debian 5.10.149-2 (2022-10-21) x86_64 GNU/Linux), though the reproduction is not minimal.
>>
>> To reproduce the bug on Arch Linux, with the packages rust, pcsclite, and openpgp-card-tools installed:
>>
>> - Compile and run the usbip runner from this PR: https://github.com/Nitrokey/nitrokey-3-firmware/pull/149 (`cd nitrokey-3-firmware/runners/usbip && cargo run --features alpha`)
>> - Run `usbip attach -r localhost -b 1-1`
>> - Run `pcscd`
>> - Run `opgpcard status`
>>
>> The bug should happen.
>>
>
> Thank you for reporting the problem. I will take a look and
> get back to you with possible fix. Will you be able to test
> fixes?
>
Please send me complete dmesg and your kernel config.
thanks,
-- Shuah
next prev parent reply other threads:[~2023-01-12 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 8:40 kernel BUG at mm/usercopy.c when using usbip Sosthène Guédon
2023-01-12 15:13 ` Shuah Khan
2023-01-12 15:40 ` Shuah Khan [this message]
2023-03-15 16:25 ` Zenithal
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=db42f90b-dec3-1e2b-c973-b4dc76cd4830@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robin@nitrokey.com \
--cc=shuah@kernel.org \
--cc=sosthene@nitrokey.com \
--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;
as well as URLs for NNTP newsgroup(s).