From: "Jose M. Guisado" <guigom@riseup.net>
To: Phil Sutter <phil@nwl.cc>
Cc: netfilter-devel@vger.kernel.org, pablo@netfilter.org, erig@erig.me
Subject: Re: [PATCH nft v4] src: enable json echo output when reading native syntax
Date: Tue, 4 Aug 2020 15:05:25 +0200 [thread overview]
Message-ID: <87971ac3-ed9c-9923-ca3f-df6dfb8b94d9@riseup.net> (raw)
In-Reply-To: <20200804123744.GV13697@orbyte.nwl.cc>
On 4/8/20 14:37, Phil Sutter wrote:
> Why not just:
>
> --- a/src/monitor.c
> +++ b/src/monitor.c
> @@ -922,8 +922,11 @@ int netlink_echo_callback(const struct nlmsghdr *nlh, void *data)
> if (!nft_output_echo(&echo_monh.ctx->nft->output))
> return MNL_CB_OK;
>
> - if (nft_output_json(&ctx->nft->output))
> - return json_events_cb(nlh, &echo_monh);
> + if (nft_output_json(&ctx->nft->output)) {
> + if (ctx->nft->json_root)
> + return json_events_cb(nlh, &echo_monh);
> + echo_monh.format = NFTNL_OUTPUT_JSON;
> + }
>
> return netlink_events_cb(nlh, &echo_monh);
> }
>
> At a first glance, this seems to work just fine.
>
> Cheers, Phil
This does not output anything on my machine. This is because json_echo
is not initialized before netlink_echo_callback.
The mock monitor is responsible of appending the appropriate json cmd
object to nft->json_echo, so we need it initialized when the case is as
we have discussed before, native input and echo+json.
In addition netlink_echo_callback is called each time we receive
something from the mnl socket. So checking if nft->json_echo is already
initialized is necessary too, if not checked only the last response is
shown, and for each past response that means a lost json_t reference to
an array of cmd objs for that given response.
Regards.
next prev parent reply other threads:[~2020-08-04 13:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 19:53 [PATCH nft] src: enable output with "nft --echo --json" and nftables syntax Jose M. Guisado Gomez
2020-07-31 0:00 ` [PATCH nft v2 0/1] " Jose M. Guisado Gomez
2020-07-31 0:00 ` [PATCH nft v2 1/1] " Jose M. Guisado Gomez
2020-07-31 9:22 ` Pablo Neira Ayuso
2020-07-31 10:49 ` [PATCH nft v3] " Jose M. Guisado Gomez
2020-08-04 10:38 ` [PATCH nft v4] src: enable json echo output when reading native syntax Jose M. Guisado Gomez
2020-08-04 11:05 ` Pablo Neira Ayuso
2020-08-04 12:13 ` Jose M. Guisado
2020-08-04 12:15 ` Pablo Neira Ayuso
2020-08-04 12:37 ` Phil Sutter
2020-08-04 13:05 ` Jose M. Guisado [this message]
2020-08-04 13:14 ` Phil Sutter
2020-08-04 13:44 ` Jose M. Guisado
2020-08-04 14:04 ` Pablo Neira Ayuso
2020-08-04 14:17 ` Pablo Neira Ayuso
2020-08-04 14:20 ` Phil Sutter
2020-08-04 15:47 ` Jose M. Guisado
2020-08-04 19:10 ` Pablo Neira Ayuso
2020-08-05 9:31 ` Phil Sutter
2020-08-05 9:45 ` Pablo Neira Ayuso
2020-08-06 7:28 ` Phil Sutter
2020-08-04 12:57 ` Eric Garver
2020-07-31 12:33 ` [PATCH nft v2 1/1] src: enable output with "nft --echo --json" and nftables syntax Phil Sutter
2020-07-31 12:58 ` Pablo Neira Ayuso
2020-07-31 13:48 ` Phil Sutter
2020-07-31 14:17 ` Eric Garver
2020-07-31 17:19 ` Pablo Neira Ayuso
2020-07-31 18:36 ` Eric Garver
2020-07-31 20:14 ` Eric Garver
2020-07-31 17:30 ` Pablo Neira Ayuso
2020-08-01 0:02 ` Phil Sutter
2020-08-01 19:27 ` Pablo Neira Ayuso
2020-08-03 12:52 ` Phil Sutter
2020-08-04 10:20 ` Jose M. Guisado
2020-08-04 10:32 ` 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=87971ac3-ed9c-9923-ca3f-df6dfb8b94d9@riseup.net \
--to=guigom@riseup.net \
--cc=erig@erig.me \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.