From: Balazs Scheidler <bazsi77@gmail.com>
To: Florian Westphal <fw@strlen.de>
Cc: Phil Sutter <phil@nwl.cc>,
Martin Gignac <martin.gignac@gmail.com>,
netfilter@vger.kernel.org,
netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: Unable to create a chain called "trace"
Date: Fri, 12 Feb 2021 19:02:21 +0100 [thread overview]
Message-ID: <20210212180221.GA3914830@bzorp> (raw)
In-Reply-To: <20210212122007.GE2766@breakpoint.cc>
On Fri, Feb 12, 2021 at 01:20:07PM +0100, Florian Westphal wrote:
> Phil Sutter <phil@nwl.cc> wrote:
> > I didn't find a better way to conditionally parse two following args as
> > strings instead of just a single one. Basically I miss an explicit end
> > condition from which to call BEGIN(0).
>
> Yes, thats part of the problem.
>
> > > Seems we need allow "{" for "*" and then count the {} nests so
> > > we can pop off a scanner state stack once we make it back to the
> > > same } level that we had at the last state switch.
> >
> > What is the problem?
>
> Detect when we need to exit the current start condition.
>
> We may not even be able to do BEGIN(0) if we have multiple, nested
> start conditionals. flex supports start condition stacks, but that
> still leaves the exit/closure issue.
>
> Example:
>
> table chain {
> chain bla { /* should start to recognize rules, but
> we did not see 'rule' keyword */
> ip saddr { ... } /* can't exit rule start condition on } ... */
> ip daddr { ... }
> } /* should disable rule keywords again */
>
> chain dynamic { /* so 'dynamic' is a string here ... */
> }
> }
>
> I don't see a solution, perhaps add dummy bison rule(s)
> to explicitly signal closure of e.g. a rule context?
You can always push/pop the flexer state from bison code blocks, maybe
that's what you mean on "dummy bison rules".
Trigger the state from bison and make sure it ends.
Something like this:
diff --git a/src/parser_bison.y b/src/parser_bison.y
index 11e899ff..d8107181 100644
--- a/src/parser_bison.y
+++ b/src/parser_bison.y
@@ -2397,7 +2397,10 @@ chain_policy : ACCEPT { $$ = NF_ACCEPT; }
identifier : STRING
;
-string : STRING
+string : { yy_push_state(scanner, STRING); } __string { yy_pop_state(scanner); }
+ ;
+
+__string : STRING
| QUOTED_STRING
| ASTERISK_STRING
;
--
Bazsi
next prev parent reply other threads:[~2021-02-12 18:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANf9dFMJN5ZsihtygUnEWB_9T=WLbEHrZY1a5mTqLgN7J39D5w@mail.gmail.com>
2021-02-08 15:49 ` Unable to create a chain called "trace" Florian Westphal
2021-02-08 16:47 ` Phil Sutter
2021-02-08 17:14 ` Florian Westphal
2021-02-09 13:56 ` Phil Sutter
2021-02-12 0:05 ` Florian Westphal
2021-02-12 11:40 ` Phil Sutter
2021-02-12 12:20 ` Florian Westphal
2021-02-12 17:09 ` Pablo Neira Ayuso
2021-02-12 17:32 ` Phil Sutter
2021-02-12 17:54 ` Pablo Neira Ayuso
2021-02-12 21:07 ` Phil Sutter
2021-02-12 18:02 ` Balazs Scheidler [this message]
2021-02-17 19:59 ` Phil Sutter
2021-02-17 20:16 ` Florian Westphal
2021-02-12 12:29 ` Florian Westphal
2021-02-12 12:48 ` Phil Sutter
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=20210212180221.GA3914830@bzorp \
--to=bazsi77@gmail.com \
--cc=fw@strlen.de \
--cc=martin.gignac@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=phil@nwl.cc \
/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).