From: Alexander Aring <aahringo@redhat.com>
To: pablo@netfilter.org
Cc: fw@strlen.de, netdev@vger.kernel.org, linux-man@vger.kernel.org,
teigland@redhat.com
Subject: [PATCH resend] netlink.7: note not reliable if NETLINK_NO_ENOBUFS
Date: Thu, 4 Mar 2021 15:57:28 -0500 [thread overview]
Message-ID: <20210304205728.34477-1-aahringo@redhat.com> (raw)
This patch adds a note to the netlink manpage that if NETLINK_NO_ENOBUFS
is set there is no additional handling to make netlink reliable. It just
disables the error notification. The used word "avoid" receiving ENOBUFS
errors can be interpreted that netlink tries to do some additional queue
handling to avoid that such scenario occurs at all, e.g. like zerocopy
which tries to avoid memory copy. However disable is not the right word
here as well that in some cases ENOBUFS can be still received. This
patch makes clear that there will no additional handling to put netlink
in a more reliable mode.
Signed-off-by: Alexander Aring <aahringo@redhat.com>
---
resend:
- forgot linux-man mailinglist in cc, sorry.
man7/netlink.7 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man7/netlink.7 b/man7/netlink.7
index c69bb62bf..2cb0d1a55 100644
--- a/man7/netlink.7
+++ b/man7/netlink.7
@@ -478,7 +478,7 @@ errors.
.\" Author: Pablo Neira Ayuso <pablo@netfilter.org>
This flag can be used by unicast and broadcast listeners to avoid receiving
.B ENOBUFS
-errors.
+errors. Note it does not turn netlink into any kind of more reliable mode.
.TP
.BR NETLINK_LISTEN_ALL_NSID " (since Linux 4.2)"
.\" commit 59324cf35aba5336b611074028777838a963d03b
--
2.26.2
next reply other threads:[~2021-03-04 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 20:57 Alexander Aring [this message]
2021-03-05 3:04 ` [PATCH resend] netlink.7: note not reliable if NETLINK_NO_ENOBUFS Pablo Neira Ayuso
2021-03-05 19:43 ` Alexander Ahring Oder Aring
2021-03-05 20:36 ` Pablo Neira Ayuso
2021-03-05 23:21 ` Florian Westphal
2021-03-06 0:10 ` Pablo Neira Ayuso
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=20210304205728.34477-1-aahringo@redhat.com \
--to=aahringo@redhat.com \
--cc=fw@strlen.de \
--cc=linux-man@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=teigland@redhat.com \
/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