[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240301012845.2951053-1-kuba@kernel.org>
Date: Thu, 29 Feb 2024 17:28:42 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: davem@...emloft.net
Cc: netdev@...r.kernel.org,
edumazet@...gle.com,
pabeni@...hat.com,
johannes@...solutions.net,
fw@...len.de,
pablo@...filter.org,
idosch@...dia.com,
jiri@...nulli.us,
Jakub Kicinski <kuba@...nel.org>
Subject: [PATCH net-next 0/3] netlink: handle EMSGSIZE errors in the core
Ido discovered some time back that we usually force NLMSG_DONE
to be delivered in a separate recv() syscall, even if it would
fit into the same skb as data messages. He made nexthop try
to fit DONE with data in commit 8743aeff5bc4 ("nexthop: Fix
infinite nexthop bucket dump when using maximum nexthop ID"),
and nobody has complained so far.
We have since also tried to follow the same pattern in new
genetlink families, but explaining to people, or even remembering
the correct handling ourselves is tedious.
Let the netlink socket layer consume -EMSGSIZE errors.
Practically speaking most families use this error code
as "dump needs more space", anyway.
Jakub Kicinski (3):
netlink: handle EMSGSIZE errors in the core
netdev: let netlink core handle -EMSGSIZE errors
genetlink: fit NLMSG_DONE into same read() as families
net/core/netdev-genl.c | 15 +++------------
net/core/page_pool_user.c | 2 --
net/netlink/af_netlink.c | 9 +++++++++
net/netlink/genetlink.c | 12 +++++++-----
4 files changed, 19 insertions(+), 19 deletions(-)
--
2.43.2
Powered by blists - more mailing lists