From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Oliver Neukum <oneukum@suse.com>,
"Purohit, Kaushal" <kaushal.purohit@ti.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: issues with cdc ncm host class driver
Date: Tue, 20 Jun 2023 16:16:20 +0200 [thread overview]
Message-ID: <19199830-33b6-2a4c-e08b-d1a76ce4c59b@leemhuis.info> (raw)
In-Reply-To: <da479ebf-b3fb-0a58-16be-07fe55d36621@leemhuis.info>
On 04.04.23 12:33, Linux regression tracking (Thorsten Leemhuis) wrote:
> Side note: there is now a bug tracking ticket for this issue, too:
> https://bugzilla.kernel.org/show_bug.cgi?id=217290
>
> On 03.04.23 12:09, Oliver Neukum wrote:
>> On 03.04.23 08:14, Purohit, Kaushal wrote:
>
>>> Referring to patch with commit ID
>>> (*e10dcb1b6ba714243ad5a35a11b91cc14103a9a9*).
>>>
>>> This is a spec violation for CDC NCM class driver. Driver clearly says
>>> the significance of network capabilities. (snapshot below)
>>>
>>> However, with the mentioned patch these values are disrespected and
>>> commands specific to these capabilities are sent from the host
>>> regardless of device' capabilities to handle them.
>>
>> Right. So for your device, the correct behavior would be to do
>> nothing, wouldn't it? The packets would be delivered and the host
>> needs to filter and discard unrequested packets.
>
> #regzbot ^introduced e10dcb1b6ba714243ad
> https://bugzilla.kernel.org/show_bug.cgi?id=217290
> #regzbot from: Purohit, Kaushal
> #regzbot title net: cdc_ncm: spec violation for CDC NCM
> #regzbot ignore-activity
Not sure what happen to this, my last inquiries were not answered, so it
seems nobody cares anymore
#regzbot inconclusive: radio silence, ignoring
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.
next prev parent reply other threads:[~2023-06-20 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <da37bb0d43de465185c10aad9924f265@ti.com>
2023-04-03 10:09 ` issues with cdc ncm host class driver Oliver Neukum
2023-04-03 10:18 ` [EXTERNAL] " Purohit, Kaushal
2023-04-04 10:33 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-20 14:16 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-06-27 6:40 ` [EXTERNAL] " Purohit, Kaushal
2023-04-05 10:53 ` Oliver Neukum
2023-04-28 8:45 ` Linux regression tracking (Thorsten Leemhuis)
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=19199830-33b6-2a4c-e08b-d1a76ce4c59b@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=kaushal.purohit@ti.com \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=regressions@lists.linux.dev \
--cc=stable@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).