From: Ivy Lopez <skunkolee@gmail.com>
To: westeri@kernel.org
Cc: andreas.noever@gmail.com, YehezkelShB@gmail.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] thunderbolt: stream: Make read return framing error to the userspace
Date: Mon, 21 Sep 2026 18:17:42 -0600 [thread overview]
Message-ID: <20260922001742.14332-1-skunkolee@gmail.com> (raw)
In-Reply-To: <20260921111921.3289289-1-mika.westerberg@linux.intel.com>
On Mon, Sep 21, 2026 at 11:19 AM UTC, Mika Westerberg wrote:
> + if (!nbytes) {
> + pr_warn("corrupted frame received, flags %#x\n",
> + sf->frame.flags);
> + tbstream_dev_consume_rx(sdev);
> + ret = -EIO;
> + }
> + break;
One question: EPOLLIN is set unconditionally in the rx callback
regardless of frame flags, and tbstream_dev_fops_poll() only checks
tbstream_ring_available() (pure ring depth), never frame flags.
EPOLLERR is used elsewhere in this file but only for device-level
invalidity, not per-frame corruption. So userspace still has no way
to learn a corrupted frame is queued via poll() before calling
read() and getting -EIO. I'm just wondering, is this intentional,
or worth a follow-up?
Also, fwiw, this doesn't apply cleanly against current usb-next for
me, git apply fails on the rx_callback hunk. Looks like it's against
a tree predating the busy-polling changes.
Not a blocker either way.
Reviewed-by: Ivy Lopez <skunkolee@gmail.com>
next parent reply other threads:[~2026-09-22 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260921111921.3289289-1-mika.westerberg@linux.intel.com>
2026-09-22 0:17 ` Ivy Lopez [this message]
2026-09-22 4:11 ` Mika Westerberg
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=20260922001742.14332-1-skunkolee@gmail.com \
--to=skunkolee@gmail.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=westeri@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
all inboxes | Powered by JetHome®