From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Arturo Borrero Gonzalez <arturo@debian.org>
Cc: James Feeney <james@nurealm.net>,
Netfilter Development Mailing list
<netfilter-devel@vger.kernel.org>
Subject: Re: reject statement - "crazy" parse error?
Date: Fri, 28 Oct 2016 11:11:20 +0200 [thread overview]
Message-ID: <20161028091120.GA3374@salvia> (raw)
In-Reply-To: <CAOkSjBgd0UJzg3Xp-ub4twebDmHdVJ25e5GkWEw5h2XUmQxKxQ@mail.gmail.com>
On Fri, Oct 28, 2016 at 11:07:24AM +0200, Arturo Borrero Gonzalez wrote:
> On 26 October 2016 at 20:50, James Feeney <james@nurealm.net> wrote:
[...]
> > Well, that's not good, because something changed, from "No such file or
> > directory" to "Operation not supported", but it is still not right. Of course,
> > in both cases, the error messages are "useless", not saying *what* file, and not
> > saying *what* operation.
> >
>
> Yes, the error reporting in the 'nft -f' situation is something to improve,
> specially with kernel reported errors.
> This is even worse in the case of nested includes.
Just for the record: I have a patch to solve this. We need to augment
the netlink error reporting infrastructure, if I add this into the
netlink core (which is where this improved error reporting
infrastructure belongs) it may take a little while though, and a bit
of code in userspace.
next prev parent reply other threads:[~2016-10-28 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 1:30 reject statement - "crazy" parse error? James Feeney
2016-10-26 7:00 ` Arturo Borrero Gonzalez
2016-10-26 18:50 ` James Feeney
2016-10-28 9:07 ` Arturo Borrero Gonzalez
2016-10-28 9:11 ` Pablo Neira Ayuso [this message]
2016-10-28 16:33 ` James Feeney
2016-10-28 19:16 ` James Feeney
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=20161028091120.GA3374@salvia \
--to=pablo@netfilter.org \
--cc=arturo@debian.org \
--cc=james@nurealm.net \
--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 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.