From: kaz1020 <kaz1020@gmail.com>
To: Antonio Messina <amessina@google.com>
Cc: linux-kernel@vger.kernel.org, davem@davemloft.net,
kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] udp: fix integer overflow while computing available space in sk_rcvbuf
Date: Tue, 9 Nov 2021 00:44:14 +0900 [thread overview]
Message-ID: <D4E91882-A53B-44CC-9741-14B19B863C9F@gmail.com> (raw)
Antonio Messina at Google,
Linux Kernel maintainers,
I read the following fraud Google Blog.
https://cloud.google.com/blog/topics/inside-google-cloud/google-cloud-support-engineer-solves-a-tough-dns-case
I require Antonio Messina the fulfillment of obligations.
Antonio Messina accepted the following requests on June 27, 2020.
I requested Antonio Messina to correct his mistakes.
- Rewrite the article on fraud Google Blog
- Send the new patch I proposed
Past, I explained the following result to Antonio Messina and Google.
Abstract:
The “size" variable of the following line will be removed.
Line: https://github.com/torvalds/linux/blob/v5.4/net/ipv4/udp.c#L1478
Because comparing "to be allocated buffer size" and "Max buffer size" + "size."
Antonio Messina's mistake: if (rmem > (unsigned int)(size + sk->sk_rcvbuf))
The fix I propose: if (rmem > sk->sk_rcvbuf)
Details:
In the function __udp_enqueue_schedule_skb.
- rmem: Same as sk->sk_rmem_alloc.
-- It means allocated or to be allocated buffer size.
- sk->sk_rcvbuf: Max buffer size(purpose to limit the buffer size).
- size: Same as skb->truesize.
-- It means a packet size.
The original problem is committed by:
https://github.com/torvalds/linux/commit/363dc73acacbbcdae98acf5612303e9770e04b1d
In addition, the condition sentence has been corrupted before this commit.
Antonio Messina sent a poor patch:
https://lkml.org/lkml/2019/12/19/482
--
Fix it,
kaz1020
next reply other threads:[~2021-11-08 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 15:44 kaz1020 [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-19 14:08 Antonio Messina
2019-12-24 22:54 ` David Miller
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=D4E91882-A53B-44CC-9741-14B19B863C9F@gmail.com \
--to=kaz1020@gmail.com \
--cc=amessina@google.com \
--cc=davem@davemloft.net \
--cc=kuznet@ms2.inr.ac.ru \
--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
all inboxes | Powered by JetHome®