From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Alexander Ahring Oder Aring <aahringo@redhat.com>,
fw@strlen.de, netdev@vger.kernel.org, linux-man@vger.kernel.org,
David Teigland <teigland@redhat.com>
Subject: Re: [PATCH resend] netlink.7: note not reliable if NETLINK_NO_ENOBUFS
Date: Sat, 6 Mar 2021 00:21:59 +0100 [thread overview]
Message-ID: <20210305232159.GB10808@breakpoint.cc> (raw)
In-Reply-To: <20210305203657.GA9426@salvia>
Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > If I understand correctly, the connection tracking netlink interface
> > is an exception here because it has its own handling of dealing with
> > congestion ("more reliable"?) so you need to disable the "default
> > congestion control"?
>
> In conntrack, you have to combine NETLINK_NO_ENOBUFS with
> NETLINK_BROADCAST_ERROR, then it's the kernel turns on the "more
> reliable" event delivery.
The "more reliable" event delivery guarantees that the kernel will
deliver at least the DESTROY notification (connection close).
If the userspace program is stuck, kernel has to hold on the expired
entries. Eventually conntrack stops accepting new connections because
the table is full.
So this feature can't be recommended as a best-practice for conntrack
either.
next prev parent reply other threads:[~2021-03-05 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 20:57 [PATCH resend] netlink.7: note not reliable if NETLINK_NO_ENOBUFS Alexander Aring
2021-03-05 3:04 ` 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 [this message]
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=20210305232159.GB10808@breakpoint.cc \
--to=fw@strlen.de \
--cc=aahringo@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).