[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <248c2ca6-0c27-dc62-6d20-49c87f0af15f@web.de>
Date: Mon, 14 Oct 2019 14:50:48 +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>,
kernel-janitors@...r.kernel.org
Cc: LKML <linux-kernel@...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
…
>> Can an other error reporting approach be nicer here?
>
> There is no error reported if kmemdup() has failed.
How do data from the Linux allocation failure report fit to this information?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/coding-style.rst?id=4f5cafb5cb8471e54afdc9054d973535614f7675#n878
> timewait is best effort.
How do you think about to return an error code like “-ENOMEM” at this place?
Regards,
Markus
Powered by blists - more mailing lists