From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Alexander Alemayhu <alexander@alemayhu.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft] mnl: continue monitor if errno is ESRCH
Date: Sun, 26 Feb 2017 21:24:10 +0100 [thread overview]
Message-ID: <20170226202410.GB1827@salvia> (raw)
In-Reply-To: <20170226163058.24754-1-alexander@alemayhu.com>
On Sun, Feb 26, 2017 at 05:30:58PM +0100, Alexander Alemayhu wrote:
> Running the test cases in the shell directory while running nft monitor results
> in nft exiting with '# ERROR: No such process'. The minimal steps where I could
> reproduce is:
>
> nft monitor # shell 1
> run-tests.sh testcases/sets/0011add_many_elements_0 # shell 2
>
> Signed-off-by: Alexander Alemayhu <alexander@alemayhu.com>
> ---
>
> Not sure if this is considered a fix or desired behaviour, but I was not
> expecting monitor to exit like this.
>
> src/mnl.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/src/mnl.c b/src/mnl.c
> index 295dd84a5840..a0066a28b44f 100644
> --- a/src/mnl.c
> +++ b/src/mnl.c
> @@ -1129,7 +1129,10 @@ int mnl_nft_event_listener(struct mnl_socket *nf_sock,
> printf("# ERROR: We lost some netlink events!\n");
> continue;
> }
> +
> fprintf(stdout, "# ERROR: %s\n", strerror(errno));
> + if (errno == ESRCH)
> + continue;
It seems netlink is returning ESRCH when the number of events is high,
however, it should hit ENOBUFS instead, this is strange.
next prev parent reply other threads:[~2017-02-26 20:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 16:30 [PATCH nft] mnl: continue monitor if errno is ESRCH Alexander Alemayhu
2017-02-26 20:24 ` Pablo Neira Ayuso [this message]
2017-03-01 11:21 ` Pablo Neira Ayuso
2017-03-01 11:41 ` Pablo Neira Ayuso
2017-03-01 14:52 ` Alexander Alemayhu
2017-03-01 15:18 ` Pablo Neira Ayuso
2017-03-01 18:27 ` Alexander Alemayhu
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=20170226202410.GB1827@salvia \
--to=pablo@netfilter.org \
--cc=alexander@alemayhu.com \
--cc=netfilter-devel@vger.kernel.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).