From: Pablo Neira Ayuso <pablo@netfilter.org>
To: prashantkumar dhotre <prashantkumardhotre@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: EPOLLERR on memory mapped netlink socket
Date: Tue, 24 Jan 2017 20:28:58 +0100 [thread overview]
Message-ID: <20170124192858.GA10240@salvia> (raw)
In-Reply-To: <CA+VDgmP9MigJxiN5snFmLdHw7cydr4JbnBDDPwzex0Tszqgaag@mail.gmail.com>
On Mon, Jan 23, 2017 at 09:20:23AM +0530, prashantkumar dhotre wrote:
[...]
> What could be cause of this and what EPOLLERR on memory mapped netlink
> socket mean.
Note that memory mapped netlink support got removed ~1 year ago:
https://patchwork.ozlabs.org/patch/584709/
next prev parent reply other threads:[~2017-01-24 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 3:50 EPOLLERR on memory mapped netlink socket prashantkumar dhotre
2017-01-23 17:40 ` prashantkumar dhotre
2017-01-24 6:52 ` Patrick PIGNOL
2017-01-24 19:28 ` Pablo Neira Ayuso [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-23 3:49 prashantkumar dhotre
2017-01-23 17:40 ` prashantkumar dhotre
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=20170124192858.GA10240@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=prashantkumardhotre@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.