From: Oliver Neukum <oneukum@suse.de>
To: David Guillen Fandos <david@davidgf.net>,
Greg KH <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org
Subject: Re: System crash/lockup after plugging CDC ACM device
Date: Tue, 21 Jul 2020 10:01:37 +0200 [thread overview]
Message-ID: <1595318497.29149.3.camel@suse.de> (raw)
In-Reply-To: <ed743fe1e0ede6d37bc4a62ba704f51c54c2f5bf.camel@davidgf.net>
Am Mittwoch, den 15.07.2020, 13:20 +0200 schrieb David Guillen Fandos:
> Shouldn't the kernel be resilient to such devices? I've developed quite
> a few USB devices in the past and I've never ran into things like this
> on Linux
Yes. Unfortunately we do not know which module is crashing here.
It may be as simple as CDC-ACM retrying without a delay or giving
up. Or this is in usbcore. Could you initially try without
CDC-ACM, so we can narrow this down? And tehn we can try with
dynamic debugging or thought what can be done.
And thank you for identifying the root cause for the malfunction.
Yet you are clearly right that even such a device should not crash the
kernel.
Regards
Oliver
prev parent reply other threads:[~2020-07-21 8:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 8:58 System crash/lockup after plugging CDC ACM device David Guillen Fandos
2020-07-15 9:30 ` Greg KH
2020-07-15 10:31 ` David Guillen Fandos
2020-07-15 10:50 ` Greg KH
2020-07-15 10:57 ` David Guillen Fandos
2020-07-15 11:12 ` Greg KH
2020-07-15 11:20 ` David Guillen Fandos
2020-07-15 12:24 ` Greg KH
2020-07-15 17:03 ` David Guillen Fandos
2020-07-15 20:39 ` Daniele Palmas
2020-07-16 14:30 ` David Guillen Fandos
2020-07-19 23:36 ` David Guillen Fandos
2020-07-20 1:21 ` Alan Stern
2020-07-20 16:55 ` Dan Williams
2020-07-20 20:39 ` David Guillen Fandos
2020-07-21 8:26 ` Greg KH
2020-07-22 14:41 ` David Guillen Fandos
2020-07-22 14:57 ` Dan Williams
2020-07-21 8:01 ` 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=1595318497.29149.3.camel@suse.de \
--to=oneukum@suse.de \
--cc=david@davidgf.net \
--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 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).