[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fc39488c-f874-5d85-3200-60001e6bda52@web.de>
Date: Mon, 14 Oct 2019 08:51:02 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Eric Dumazet <eric.dumazet@...il.com>, netdev@...r.kernel.org,
Alexei Starovoitov <ast@...nel.org>,
Alexey Kuznetsov <kuznet@....inr.ac.ru>,
Daniel Borkmann <daniel@...earbox.net>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Hideaki Yoshifuji <yoshfuji@...ux-ipv6.org>,
Martin KaFai Lau <kafai@...com>,
Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>
Cc: LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org, Aditya Pakki <pakki001@....edu>,
Kangjie Lu <kjlu@....edu>, Navid Emamdoost <emamd001@....edu>,
Stephen McCamant <smccaman@....edu>
Subject: Re: tcp: Checking a kmemdup() call in tcp_time_wait()
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/ipv4/tcp_minisocks.c?id=1c0cc5f1ae5ee5a6913704c0d75a6e99604ee30a#n306
>> https://elixir.bootlin.com/linux/v5.4-rc2/source/net/ipv4/tcp_minisocks.c#L306
…
> Presumably the BUG would trigger if a really disturbing bug happened.
How “buggy” is this place if the function call “kmemdup” failed?
Can an other error reporting approach be nicer here?
Regards,
Markus
Powered by blists - more mailing lists