From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Florian Westphal <fw@strlen.de>,
netfilter-devel@vger.kernel.org, Eric Garver <eric@garver.life>
Subject: Re: [PATCH nft] src: mnl: fix --echo buffer size -- again
Date: Tue, 10 Sep 2019 13:44:12 +0200 [thread overview]
Message-ID: <20190910114412.GA22704@breakpoint.cc> (raw)
In-Reply-To: <20190910112254.isfbdqjfg6aokcm7@salvia>
Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> I'd still like to keep setting the receive buffer for the non-echo
> case, a ruleset with lots of acknowledments (lots of errors) might hit
> ENOBUFS, I remember that was reproducible.
>
> Probably this? it's based on your patch.
LGTM, feel free to apply this.
next prev parent reply other threads:[~2019-09-10 11:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 22:19 [PATCH nft] src: mnl: fix --echo buffer size -- again Florian Westphal
2019-09-10 8:50 ` Pablo Neira Ayuso
2019-09-10 10:52 ` Florian Westphal
2019-09-10 11:22 ` Pablo Neira Ayuso
2019-09-10 11:44 ` Florian Westphal [this message]
2019-09-10 13:08 ` Eric Garver
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=20190910114412.GA22704@breakpoint.cc \
--to=fw@strlen.de \
--cc=eric@garver.life \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/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).