From: David Howells <dhowells@redhat.com>
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: dhowells@redhat.com, netdev@vger.kernel.org, mrpre@163.com,
syzbot+de6565462ab540f50e47@syzkaller.appspotmail.com,
Eric Dumazet <edumazet@google.com>,
Neal Cardwell <ncardwell@google.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
"David S. Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4] tcp: Correct signedness in skb remaining space calculation
Date: Tue, 08 Jul 2025 14:11:14 +0100 [thread overview]
Message-ID: <2554853.1751980274@warthog.procyon.org.uk> (raw)
In-Reply-To: <20250707054112.101081-1-jiayuan.chen@linux.dev>
Jiayuan Chen <jiayuan.chen@linux.dev> wrote:
> The types of the variables involved are:
> '''
> copy: ssize_t (s64 on 64-bit systems)
> size_goal: int
> skb->len: unsigned int
> '''
>
> Due to C's type promotion rules, the signed size_goal is converted to an
> unsigned int to match skb->len before the subtraction. The result is an
> unsigned int.
>
> When this unsigned int result is then assigned to the s64 copy variable,
> it is zero-extended, preserving its non-negative value. Consequently, copy
> is always >= 0.
Ewww.
Would it be better to explicitly force the subtraction to be signed, e.g.:
skb = tcp_write_queue_tail(sk);
if (skb)
copy = size_goal - (ssize_t)skb->len;
rather than relying on getting it right with an implicit conversion to a
signed int of the same size?
If not, is it worth sticking in a comment to note the potential issue?
David
next prev parent reply other threads:[~2025-07-08 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 5:41 [PATCH net-next v4] tcp: Correct signedness in skb remaining space calculation Jiayuan Chen
2025-07-07 7:21 ` Eric Dumazet
2025-07-08 13:11 ` David Howells [this message]
2025-07-08 13:14 ` Eric Dumazet
2025-07-08 14:30 ` Jakub Kicinski
2025-07-08 14:44 ` David Howells
2025-07-08 15:10 ` patchwork-bot+netdevbpf
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=2554853.1751980274@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiayuan.chen@linux.dev \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrpre@163.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+de6565462ab540f50e47@syzkaller.appspotmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.