From: Patrick McHardy <kaber@trash.net>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org
Subject: [PATCH 0/8] nftables: fix and improve error reporting
Date: Tue, 4 Feb 2014 08:35:12 +0000 [thread overview]
Message-ID: <1391502920-19186-1-git-send-email-kaber@trash.net> (raw)
The following patchset fixes a couple of minor issues and improves
error reporting:
- don't show "In file included from internal:0:0-0:" for files parsed with -f
- location fixes
- fix output of implicit relational ops for constant LHS or non-constant RHS
- add missing closing of scope on parsing errors of blocks
- recover from errors in blocks and continue parsing
- evaluate every command immediately after parsing it
The goal of this patchset is to make error reporting show multiple errors
at once so testing and fixing of a ruleset can be done more quickly.
With these patches, we output all errors encountered during parsing and
evaluation in one batch:
tests/error.1:4:8-8: Error: syntax error, unexpected '{', expecting string
filter {
^
tests/error.1:5:13-13: Error: syntax error, unexpected newline
filter input
^
tests/error.1:6:17-17: Error: syntax error, unexpected newline
filter input tcp
^
tests/error.1:7:23-23: Error: syntax error, unexpected newline
filter input tcp dport
^
tests/error.1:8:24-26: Error: datatype mismatch, expected internet network service, expression has type Internet protocol
filter input tcp dport tcp
~~~~~~~~~ ^^^
tests/error.1:9:24-32: Error: Right hand side of relational expression (==) must be constant
filter input tcp dport tcp dport
~~~~~~~~~~^^^^^^^^^
I'll push this shortly unless I hear objections.
Patrick McHardy (8):
evaluate: determine implicit relational op before RHS constant checks
scanner: don't update location's line_offset for newlines
scanner: update last_line in struct location
erec: skip includes with INDESC_INTERNAL
parser: close scope when encountering an error in a table or chain block
parser: recover from errors in any block
parser: evaluate commands immediately after parsing
tests: add two tests for error reporting
include/nftables.h | 1 +
include/parser.h | 2 ++
include/rule.h | 2 +-
src/erec.c | 4 +++-
src/evaluate.c | 35 ++++++++++++-----------------------
src/main.c | 11 +++--------
src/parser.y | 27 ++++++++++++++++++++++-----
src/scanner.l | 2 +-
tests/error.1 | 9 +++++++++
tests/error.2 | 18 ++++++++++++++++++
10 files changed, 72 insertions(+), 39 deletions(-)
next reply other threads:[~2014-02-04 8:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 8:35 Patrick McHardy [this message]
2014-02-04 8:35 ` [PATCH 1/8] evaluate: determine implicit relational op before RHS constant checks Patrick McHardy
2014-02-04 8:35 ` [PATCH 2/8] scanner: don't update location's line_offset for newlines Patrick McHardy
2014-02-04 8:35 ` [PATCH 3/8] scanner: update last_line in struct location Patrick McHardy
2014-02-04 8:35 ` [PATCH 4/8] erec: skip includes with INDESC_INTERNAL Patrick McHardy
2014-02-04 8:35 ` [PATCH 5/8] parser: close scope when encountering an error in a table or chain block Patrick McHardy
2014-02-04 8:35 ` [PATCH 6/8] parser: recover from errors in any block Patrick McHardy
2014-02-04 8:35 ` [PATCH 7/8] parser: evaluate commands immediately after parsing Patrick McHardy
2014-02-04 8:35 ` [PATCH 8/8] tests: add two tests for error reporting Patrick McHardy
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=1391502920-19186-1-git-send-email-kaber@trash.net \
--to=kaber@trash.net \
--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).