From: Al Viro <viro@zeniv.linux.org.uk>
To: Alexander Vorwerk <alexander.vorwerk@stud.uni-goettingen.de>
Cc: edumazet@google.com, davem@davemloft.net,
yoshfuji@linux-ipv6.org, dsahern@kernel.org, kuba@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: ipv4: tcp.c: fix an assignment in an if condition
Date: Sat, 12 Mar 2022 17:19:18 +0000 [thread overview]
Message-ID: <YizWFod6LIhIWXmK@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <20220312162744.32318-1-alexander.vorwerk@stud.uni-goettingen.de>
On Sat, Mar 12, 2022 at 05:27:44PM +0100, Alexander Vorwerk wrote:
> reported by checkpatch.pl
... nicely demonstrating why checkpatch.pl is a menace.
> Signed-off-by: Alexander Vorwerk <alexander.vorwerk@stud.uni-goettingen.de>
> ---
> net/ipv4/tcp.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c
> index 28ff2a820f7c..7fa6e7e6ea80 100644
> --- a/net/ipv4/tcp.c
> +++ b/net/ipv4/tcp.c
> @@ -959,10 +959,10 @@ static struct sk_buff *tcp_build_frag(struct sock *sk, int size_goal, int flags,
> struct sk_buff *skb = tcp_write_queue_tail(sk);
> struct tcp_sock *tp = tcp_sk(sk);
> bool can_coalesce;
> - int copy, i;
> + int copy = size_goal - skb->len;
> + int i;
>
> - if (!skb || (copy = size_goal - skb->len) <= 0 ||
> - !tcp_skb_can_collapse_to(skb)) {
> + if (!skb || copy <= 0 || !tcp_skb_can_collapse_to(skb)) {
What is going to happen when you variant runs into
skb == NULL? And if for some reason that cannot happen, where
is the explanation of that reason?
IOW, this patch ends up quietly introducing a bug, with
no better rationale than "checkpatch.pl pointed me to that line".
NAKed-by: Al Viro <viro@zeniv.linux.org.uk>
next prev parent reply other threads:[~2022-03-12 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 16:27 [PATCH] net: ipv4: tcp.c: fix an assignment in an if condition Alexander Vorwerk
2022-03-12 17:19 ` Al Viro [this message]
2022-03-12 17:19 ` Stephen Hemminger
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=YizWFod6LIhIWXmK@zeniv-ca.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=alexander.vorwerk@stud.uni-goettingen.de \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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