From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Fernando Luis Vázquez Cao" <fernando_b1@lab.ntt.co.jp>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
linux-man@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org,
Patrick McHardy <kaber@trash.net>,
Hirotaka Sasaki <sasaki.hirotaka@lab.ntt.co.jp>
Subject: Re: [PATCH 1/2] man/send(2): add EPERM to the list of possible errors
Date: Wed, 27 Mar 2013 18:42:08 +0100 [thread overview]
Message-ID: <20130327174207.GA5725@localhost> (raw)
In-Reply-To: <1363675513.4767.6.camel@nexus>
On Tue, Mar 19, 2013 at 03:45:13PM +0900, Fernando Luis Vázquez Cao wrote:
> Subject: [PATCH 1/2] man/send(2): add EPERM to the list of possible errors
>
> System policy (for example netfilter rule) can cause a send* operation
> to fail with EPERM.
>
> Reported-by: Hirotaka Sasaki <sasaki.hirotaka@lab.ntt.co.jp>
> Signed-off-by: Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>
Acked-by: Pablo Neira Ayuso <pablo@netfilter.org>
next prev parent reply other threads:[~2013-03-27 17:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 6:45 [PATCH 1/2] man/send(2): add EPERM to the list of possible errors Fernando Luis Vázquez Cao
2013-03-19 6:52 ` [PATCH 2/2] man/send(2): document a long standing bug that can cause spurious EPERM errors Fernando Luis Vázquez Cao
2013-03-19 10:12 ` Pablo Neira Ayuso
2013-03-21 5:07 ` Fernando Luis Vazquez Cao
2013-03-26 8:37 ` [PATCH 1/2] man/send(2): add EPERM to the list of possible errors Fernando Luis Vazquez Cao
2013-03-26 10:48 ` Pablo Neira Ayuso
2013-03-27 4:14 ` Fernando Luis Vazquez Cao
2013-03-27 17:51 ` Pablo Neira Ayuso
2013-03-28 5:37 ` Fernando Luis Vazquez Cao
2013-03-27 17:42 ` Pablo Neira Ayuso [this message]
2013-03-28 2:46 ` Fernando Luis Vazquez Cao
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=20130327174207.GA5725@localhost \
--to=pablo@netfilter.org \
--cc=fernando_b1@lab.ntt.co.jp \
--cc=kaber@trash.net \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=sasaki.hirotaka@lab.ntt.co.jp \
/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.