From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Fernando Fernandez Mancera <ffmancera@riseup.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft] json: fix type mismatch on "ct expect" json exporting
Date: Fri, 13 Sep 2019 18:30:19 +0200 [thread overview]
Message-ID: <20190913163019.f6obvgaiw2qr6rgc@salvia> (raw)
In-Reply-To: <20190913115658.10330-1-ffmancera@riseup.net>
On Fri, Sep 13, 2019 at 01:56:59PM +0200, Fernando Fernandez Mancera wrote:
> The size field in ct_expect struct should be parsed as json integer and not as
> a string. Also, l3proto field is parsed as string and not as an integer. That
> was causing a segmentation fault when exporting "ct expect" objects as json.
Applied, thanks Fernando.
next prev parent reply other threads:[~2019-09-13 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 11:56 [PATCH nft] json: fix type mismatch on "ct expect" json exporting Fernando Fernandez Mancera
2019-09-13 16:30 ` Pablo Neira Ayuso [this message]
2019-09-13 19:06 ` Stéphane Veyret
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=20190913163019.f6obvgaiw2qr6rgc@salvia \
--to=pablo@netfilter.org \
--cc=ffmancera@riseup.net \
--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).