From: Florian Westphal <fw@strlen.de>
To: Phil Sutter <phil@nwl.cc>, Florian Westphal <fw@strlen.de>,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH iptables-nft 1/3] xlate: get rid of escape_quotes
Date: Thu, 24 Nov 2022 16:43:09 +0100 [thread overview]
Message-ID: <20221124154309.GE2753@breakpoint.cc> (raw)
In-Reply-To: <Y396RKuevTLC7f4+@orbyte.nwl.cc>
Phil Sutter <phil@nwl.cc> wrote:
> On Thu, Nov 24, 2022 at 02:49:37PM +0100, Florian Westphal wrote:
> > Its not necessary to escape " characters, we can simply
> > let xtables-translate print the entire translation/command
> > enclosed in '' chracters, i.e. nft 'add rule ...', this also takes
> > care of [, { and other special characters that some shells might
> > parse otherwise (when copy-pasting translated output).
> >
> > This breaks all xlate test cases, fixup in followup patches.
> >
> > Signed-off-by: Florian Westphal <fw@strlen.de>
> > ---
> [...]
> > diff --git a/include/xtables.h b/include/xtables.h
> > index 9eba4f619d35..150d40bfafd9 100644
> > --- a/include/xtables.h
> > +++ b/include/xtables.h
> > @@ -211,14 +211,12 @@ struct xt_xlate_mt_params {
> > const void *ip;
> > const struct xt_entry_match *match;
> > int numeric;
> > - bool escape_quotes;
> > };
> >
> > struct xt_xlate_tg_params {
> > const void *ip;
> > const struct xt_entry_target *target;
> > int numeric;
> > - bool escape_quotes;
> > };
>
> Does this break ABI compatibility?
Yes. I can keep the bool as a dead member if you prefer.
> > if (ret)
> > - printf("%s\n", xt_xlate_get(xl));
> > + printf("%s", xt_xlate_get(xl));
> >
> > + puts("'");
> > xt_xlate_free(xl);
> > return ret;
> > }
>
> If h->ops->xlate() fails, the code prints "'\n". How about:
>
> | if (ret)
> | printf("%s'\n", xt_xlate_get(xl));
>
> Or am I missing something?
We already printed 'insert rule, hence it was weird for the '\n' to be missed, but I see that
the caller will print a ' # iptables-syntax' in that case, so I will
re-add the '\n' to where it was.
> > if (set[0]) {
> > - printf("add set %s %s %s\n", family2str[h->family], p->table,
> > + printf("'add set %s %s %s'\n", family2str[h->family], p->table,
> > xt_xlate_set_get(xl));
>
> Quoting needs to respect cs->restore value, no? Maybe simpler to
> introduce 'const char *tick = cs->restore ? "" : "'";' and just insert
> it everywhere needed.
Will do that.
next prev parent reply other threads:[~2022-11-24 15:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 13:49 [PATCH iptables-nft 0/3] remove escape_quotes support Florian Westphal
2022-11-24 13:49 ` [PATCH iptables-nft 1/3] xlate: get rid of escape_quotes Florian Westphal
2022-11-24 14:05 ` Phil Sutter
2022-11-24 15:43 ` Florian Westphal [this message]
2022-11-24 13:49 ` [PATCH iptables-nft 2/3] extensions: change expected output for new format Florian Westphal
2022-11-24 13:49 ` [PATCH iptables-nft 3/3] extensions: remove trailing spaces Florian Westphal
2022-11-24 14:18 ` Phil Sutter
2022-11-24 15:44 ` Florian Westphal
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=20221124154309.GE2753@breakpoint.cc \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.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 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).