From: Greg KH <gregkh@linuxfoundation.org>
To: bugzilla-daemon@kernel.org
Cc: linux-usb@vger.kernel.org
Subject: Re: [Bug 220422] New: USB: Misdecoded serial number from Dymo Twin Turbo (0922:0018) breaks multi-device support in CUPS
Date: Thu, 7 Aug 2025 17:04:30 +0100 [thread overview]
Message-ID: <2025080747-despise-ferry-1da5@gregkh> (raw)
In-Reply-To: <bug-220422-208809@https.bugzilla.kernel.org/>
On Thu, Aug 07, 2025 at 01:46:44AM +0000, bugzilla-daemon@kernel.org wrote:
> **Expected Behavior:**
> The kernel should decode USB string descriptors defensively, including recovery
> from common misalignment issues in UTF-16LE encoding. Devices that return
> malformed descriptors should still expose unique serial numbers if the raw data
> permits recovery.
The device should be fixed instead, how did this device pass the USB-IF
testing framework?
thanks,
greg k-h
next prev parent reply other threads:[~2025-08-07 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 1:46 [Bug 220422] New: USB: Misdecoded serial number from Dymo Twin Turbo (0922:0018) breaks multi-device support in CUPS bugzilla-daemon
2025-08-07 1:48 ` [Bug 220422] " bugzilla-daemon
2025-08-07 16:04 ` Greg KH [this message]
2025-08-07 16:04 ` bugzilla-daemon
2025-08-07 18:32 ` bugzilla-daemon
2025-08-08 0:45 ` bugzilla-daemon
2025-10-02 3:02 ` bugzilla-daemon
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=2025080747-despise-ferry-1da5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bugzilla-daemon@kernel.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