From: "Jose M. Guisado" <guigom@riseup.net>
To: Gopal Yadav <gopunop@gmail.com>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 1/1] Solves Bug 1462 - `nft -j list set` does not show counters
Date: Tue, 6 Oct 2020 12:33:41 +0200 [thread overview]
Message-ID: <2c604efb-39a3-41de-f0a6-a44c703a20df@riseup.net> (raw)
In-Reply-To: <20201003125841.5138-1-gopunop@gmail.com>
Hi Gopal,
On 3/10/20 14:58, Gopal Yadav wrote:
> Solves Bug 1462 - `nft -j list set` does not show counters
>
> Signed-off-by: Gopal Yadav <gopunop@gmail.com>
> ---
> src/json.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/src/json.c b/src/json.c
> index 5856f9fc..6ad48fdd 100644
> --- a/src/json.c
> +++ b/src/json.c
> @@ -589,7 +589,7 @@ json_t *set_elem_expr_json(const struct expr *expr, struct output_ctx *octx)
> return NULL;
>
> /* these element attributes require formal set elem syntax */
> - if (expr->timeout || expr->expiration || expr->comment) {
> + if (expr->timeout || expr->expiration || expr->comment || expr->stmt) {
> root = json_pack("{s:o}", "val", root);
>
> if (expr->timeout) {
> @@ -604,6 +604,10 @@ json_t *set_elem_expr_json(const struct expr *expr, struct output_ctx *octx)
> tmp = json_string(expr->comment);
> json_object_set_new(root, "comment", tmp);
> }
> + if(expr->stmt) {
> + tmp = expr->stmt->ops->json(expr->stmt, octx);
You can compact this using stmt_print_json
> + json_object_update(root, tmp);
ASAN reports memleaks when using json_object_update. You should use
json_object_update_new, or maybe json_object_update_missing_new to
ensure only new keys are created.
> + }
> return json_pack("{s:o}", "elem", root);
> }
>
>
next prev parent reply other threads:[~2020-10-06 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-03 12:58 [PATCH 1/1] Solves Bug 1462 - `nft -j list set` does not show counters Gopal Yadav
2020-10-06 10:33 ` Jose M. Guisado [this message]
2020-10-06 12:42 ` Gopal Yadav
2020-10-06 13:45 ` Jose M. Guisado
2020-10-07 6:28 ` 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=2c604efb-39a3-41de-f0a6-a44c703a20df@riseup.net \
--to=guigom@riseup.net \
--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).