From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3 1/1] docparse: Escape backslash, tab and double quote in JSON
Date: Tue, 4 May 2021 15:10:58 +0200 [thread overview]
Message-ID: <YJFH4vLeaXnc8mzN@yuki> (raw)
In-Reply-To: <20210504125729.18781-1-pvorel@suse.cz>
Hi!
> +static inline void data_fprintf_esc(FILE *f, unsigned int padd, const char *str)
> +{
> + while (padd-- > 0)
> + fputc(' ', f);
> +
> + fputc('"', f);
> +
> + while (*str) {
> + switch (*str) {
> + case '\\':
> + fputs("\\\\", f);
> + break;
> + case '"':
> + fputs("\\\"", f);
> + break;
> + case '\t':
> + fputs("\\t", f);
> + break;
> + default:
> + putc(*str, f);
> + break;
> + }
> + str++;
> + }
> +
> + fputc('"', f);
> +}
Also does this even escape newlines? If you write "\n" in C it's stored
in memory as [0x0a, 0x00], no actual \ are stored in the string. What
the '\\' case does it to escape literal backslash i.e. "\\" which is
stored as [0x5c, 0x00]. Looking at JSON specification anything that is
in ascii before 0x20 (space) is invalid character in a JSON string. I
guess that the safest to write strings would be:
...
default:
if (*str >= 20)
putc(*str, f);
}
And we would have to add escape at least for '\n' the same way we have
for '\t' in the switch.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2021-05-04 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 12:57 [LTP] [PATCH v3 1/1] docparse: Escape backslash, tab and double quote in JSON Petr Vorel
2021-05-04 13:10 ` Cyril Hrubis [this message]
2021-05-04 14:44 ` Petr Vorel
2021-05-04 14:57 ` Cyril Hrubis
2021-05-06 7:50 ` Petr Vorel
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=YJFH4vLeaXnc8mzN@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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