From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Varsha Rao <rvarsha016@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft] src: Pass stateless, numeric, ip2name and handle variables as structure members.
Date: Thu, 15 Jun 2017 14:23:02 +0200 [thread overview]
Message-ID: <20170615122302.GA19582@salvia> (raw)
In-Reply-To: <CAAFX7JQk7A-T=fex8byZk0LRanAooZaTBrSGX5BjXmXEYPynVw@mail.gmail.com>
On Thu, Jun 15, 2017 at 04:58:26PM +0530, Varsha Rao wrote:
> On Thu, Jun 15, 2017 at 3:16 PM, Pablo Neira Ayuso wrote:
> > On Thu, Jun 15, 2017 at 01:01:57AM +0530, Varsha Rao wrote:
> >> diff --git a/include/datatype.h b/include/datatype.h
> >> index 04b7d88..748688e 100644
> >> --- a/include/datatype.h
> >> +++ b/include/datatype.h
> >> @@ -145,7 +145,8 @@ struct datatype {
> >> const char *desc;
> >> const struct datatype *basetype;
> >> const char *basefmt;
> >> - void (*print)(const struct expr *expr);
> >> + void (*print)(const struct expr *expr,
> >> + struct print_ctx *ct);
> >
> > Could you use:
> >
> > struct print_ctx *pctx
> >
> > instead?
> >
> > 'ct' usually refers to the connection tracking system (ct) in our
> > codebase, so I would prefer we have a different variable name.
> >
> > This applies everywhere in this patch.
>
> Okay, I will change it.
> >
> >> --- a/include/expression.h
> >> +++ b/include/expression.h
> >> @@ -157,7 +157,8 @@ struct expr_ops {
> >> void (*set_type)(const struct expr *expr,
> >> const struct datatype *dtype,
> >> enum byteorder byteorder);
> >> - void (*print)(const struct expr *expr);
> >> + void (*print)(const struct expr *expr,
> >> + struct print_ctx *ct);
> >> bool (*cmp)(const struct expr *e1,
> >> const struct expr *e2);
> >> void (*pctx_update)(struct proto_ctx *ctx,
> >> @@ -330,7 +331,7 @@ extern struct expr *expr_alloc(const struct location *loc,
> >> extern struct expr *expr_clone(const struct expr *expr);
> >> extern struct expr *expr_get(struct expr *expr);
> >> extern void expr_free(struct expr *expr);
> >> -extern void expr_print(const struct expr *expr);
> >> +extern void expr_print(const struct expr *expr, struct print_ctx *ct);
> >> extern bool expr_cmp(const struct expr *e1, const struct expr *e2);
> >> extern void expr_describe(const struct expr *expr);
> >>
> >> @@ -410,7 +411,7 @@ extern struct expr *list_expr_alloc(const struct location *loc);
> >>
> >> extern struct expr *set_expr_alloc(const struct location *loc);
> >> extern int set_to_intervals(struct list_head *msgs, struct set *set,
> >> - struct expr *init, bool add);
> >> + struct expr *init, bool add, struct print_ctx *ct);
> >
> > Why do we need this? I think we only need print_ctx for *_print()
> > functions.
>
> In src/segtree.c, set_to_intervals calls expr_print() if segtree_debug()
> is true and it would cause problem if NULL is passed to expr_print().
I see.
_debug() call should not rely on the option, so I suggest you pass a
dummy print_ctx, ie.
struct print_ctx dummy_pctx = {};
expr_print(..., &dummy_pctx);
but only for debug codepath. OK?
Thanks!
prev parent reply other threads:[~2017-06-15 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 19:31 [PATCH nft] src: Pass stateless, numeric, ip2name and handle variables as structure members Varsha Rao
2017-06-15 9:46 ` Pablo Neira Ayuso
2017-06-15 11:28 ` Varsha Rao
2017-06-15 12:23 ` Pablo Neira Ayuso [this message]
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=20170615122302.GA19582@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=rvarsha016@gmail.com \
/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).