From: Florian Westphal <fw@strlen.de>
To: Gopal Yadav <gopunop@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nftables] TODO: Replace yy_switch_to_buffer by yypop_buffer_state and yypush_buffer_state
Date: Wed, 9 Sep 2020 14:23:54 +0200 [thread overview]
Message-ID: <20200909122354.GP7319@breakpoint.cc> (raw)
In-Reply-To: <CAAUOv8iRkeAVDn3UK8DHju+-RvWViopGajN_+9y+Rm30pTWa+A@mail.gmail.com>
Gopal Yadav <gopunop@gmail.com> wrote:
> Hi Netfilter Team,
>
> I am looking to resolve a todo task in function yy_switch_to_buffer in
> nftables/src/scanner.c file.
> I am not familiar with lex but searching around I found that scanner.c
> is produced by lex according to the scanner.l file.
> Therefore my guess is, changing the scanner.c file directly is not the
> solution, right?
Right.
> Changes would have to be done in scanner.l, right?
No.
> How should I proceed to complete this todo?
This TODO is coming from flex itself, so, this is not an nftables
task.
> I browsed bugzilla to find some other issues to solve, but I feel
> lost. Are there any beginner friendly issues to solve or any other
> starting point?
This one for example:
https://bugzilla.netfilter.org/show_bug.cgi?id=1305
Its "just" a documentation issue. You could work from comment 4
and improve the nft documentation to clarify 'accept' behaviour.
For many other bugs it would help if we had testcases that demonstrated
this problem in the nftables.git repo.
So, if you can translate a BZ ticker to e.g. a new test case in
tests/shell that show problem still exists in current nftables.git then
you could submit that test case as a patch, even if the problem is not
yet resolved.
Readily available test reproducers help a lot.
next prev parent reply other threads:[~2020-09-09 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 13:05 [nftables] TODO: Replace yy_switch_to_buffer by yypop_buffer_state and yypush_buffer_state Gopal Yadav
2020-09-09 12:23 ` Florian Westphal [this message]
2020-09-09 16:10 ` Gopal Yadav
2020-09-11 18:19 ` Gopal Yadav
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=20200909122354.GP7319@breakpoint.cc \
--to=fw@strlen.de \
--cc=gopunop@gmail.com \
--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 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).