From: Patrick McHardy <kaber@trash.net>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH 0/3] netfilter: propagate routing and XFRM errors
Date: Fri, 5 Apr 2013 18:41:09 +0200 [thread overview]
Message-ID: <1365180072-6182-1-git-send-email-kaber@trash.net> (raw)
These patches fix a long standing annoyance: netfilter will return
EPERM for all errors during rerouting or XFRM policy lookups.
These patches change {ip,ip6}_route_me_harder() and nf_xfrm_me_harder()
to return errno codes and use NF_DROP_ERR() to propagate those back
to userspace.
Please apply.
next reply other threads:[~2013-04-05 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 16:41 Patrick McHardy [this message]
2013-04-05 16:41 ` [PATCH 1/3] netfilter: ipv4: propagate routing errors from ip_route_me_harder() Patrick McHardy
2013-04-05 16:41 ` [PATCH 2/3] netfilter: ipv6: propagate routing errors from ip6_route_me_harder() Patrick McHardy
2013-04-05 16:41 ` [PATCH 3/3] netfilter: nat: propagate errors from xfrm_me_harder() Patrick McHardy
2013-04-06 12:02 ` [PATCH 0/3] netfilter: propagate routing and XFRM errors 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=1365180072-6182-1-git-send-email-kaber@trash.net \
--to=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--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).