From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft,v3 2/7] mnl: mnl_set_rcvbuffer() skips buffer size update if it is too small
Date: Fri, 31 May 2019 11:30:12 +0200 [thread overview]
Message-ID: <20190531093012.GH31548@orbyte.nwl.cc> (raw)
In-Reply-To: <20190530111246.14550-1-pablo@netfilter.org>
Hi Pablo,
On Thu, May 30, 2019 at 01:12:46PM +0200, Pablo Neira Ayuso wrote:
> Check for existing buffer size, if this is larger than the newer buffer
> size, skip this size update.
>
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> ---
> v3: 'len' variable was not properly set.
>
> src/mnl.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/src/mnl.c b/src/mnl.c
> index 288a887df097..2270a084ad29 100644
> --- a/src/mnl.c
> +++ b/src/mnl.c
> @@ -235,8 +235,15 @@ static void mnl_set_sndbuffer(const struct mnl_socket *nl,
>
> static int mnl_set_rcvbuffer(const struct mnl_socket *nl, size_t bufsiz)
> {
> + unsigned int cur_bufsiz;
> + socklen_t len = sizeof(cur_bufsiz);
> int ret;
>
> + ret = getsockopt(mnl_socket_get_fd(nl), SOL_SOCKET, SO_RCVBUF,
> + &cur_bufsiz, &len);
> + if (cur_bufsiz > bufsiz)
> + return 0;
> +
For mnl_set_sndbuffer(), there is simply a global static variable
holding the last set value. Can't we use that here as well? I think of
something like:
+ static unsigned int nlsndbufsiz;
static int mnl_set_rcvbuffer(const struct mnl_socket *nl, size_t bufsiz)
{
+ socklen_t len = sizeof(nlsndbufsiz);
int ret;
+ if (!nlsndbufsiz)
+ ret = getsockopt(mnl_socket_get_fd(nl), SOL_SOCKET, SO_RCVBUF,
+ &nlsndbufsiz, &len);
+ if (nlsndbufsiz >= bufsiz)
+ return 0;
Cheers, Phil
next prev parent reply other threads:[~2019-05-31 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 11:12 [PATCH nft,v3 2/7] mnl: mnl_set_rcvbuffer() skips buffer size update if it is too small Pablo Neira Ayuso
2019-05-31 9:30 ` Phil Sutter [this message]
2019-05-31 9:59 ` 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=20190531093012.GH31548@orbyte.nwl.cc \
--to=phil@nwl.cc \
--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