From: Pavel Begunkov <[email protected]>
To: Dan Carpenter <[email protected]>
Cc: [email protected]
Subject: Re: [bug report] io_uring/net: simplify compat selbuf iov parsing
Date: Fri, 28 Feb 2025 12:22:18 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 2/28/25 09:19, Dan Carpenter wrote:
> Hello Pavel Begunkov,
>
> Commit c30f89f1d08b ("io_uring/net: simplify compat selbuf iov
> parsing") from Feb 26, 2025 (linux-next), leads to the following
> Smatch static checker warning:
Thanks for the report, it should already be fixed up in the tree.
The check is not needed, it's inconsistent with the !COMPAT path,
and import_ubuf() should verify the len for us.
--
Pavel Begunkov
prev parent reply other threads:[~2025-02-28 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 9:19 [bug report] io_uring/net: simplify compat selbuf iov parsing Dan Carpenter
2025-02-28 12:22 ` Pavel Begunkov [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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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