From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] readkey: shrink table of known escape sequences in size
Date: Wed, 30 Sep 2020 09:31:10 +0200 [thread overview]
Message-ID: <20200930073110.GF11648@pengutronix.de> (raw)
In-Reply-To: <20200928123942.26970-1-a.fatoum@pengutronix.de>
On Mon, Sep 28, 2020 at 02:39:42PM +0200, Ahmad Fatoum wrote:
> Instead of storing pointers to 4-byte strings, we could just store the
> characters directly in the struct. Can save us up to 18 pointers worth
> of space.
>
> We could save 18 x 1 byte more of static storage by making the strings
> 3 bytes of length as the nul byte need not be stored explicitly for
> strings of maximal length.
>
> For clarity, this optimization is omitted for now. We still use strncmp,
> instead of strcmp use runs risk of accidental out of bounds reads when
> longer escape sequences are added. This can't occur with strncmp.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> v1 -> v2:
> - Maintain a nul delimiter always at the cost of 18 more bytes
> (Sascha)
> ---
> lib/readkey.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/lib/readkey.c b/lib/readkey.c
> index c26e9d51aba9..6a4ddf14a99d 100644
> --- a/lib/readkey.c
> +++ b/lib/readkey.c
> @@ -20,8 +20,10 @@
> #include <linux/ctype.h>
> #include <readkey.h>
>
> +#define MAX_ESC_LEN 4
> +
> struct esc_cmds {
> - const char *seq;
> + const char seq[MAX_ESC_LEN];
> unsigned char val;
> };
>
> @@ -49,7 +51,7 @@ static const struct esc_cmds esccmds[] = {
> int read_key(void)
> {
> unsigned char c;
> - unsigned char esc[5];
> + unsigned char esc[MAX_ESC_LEN + 2];
> c = getchar();
>
> if (c == 27) {
> @@ -67,7 +69,7 @@ int read_key(void)
> }
> esc[i] = 0;
> for (i = 0; i < ARRAY_SIZE(esccmds); i++){
> - if (!strcmp(esc, esccmds[i].seq))
> + if (!strncmp(esc, esccmds[i].seq, MAX_ESC_LEN))
> return esccmds[i].val;
strncmp() gives you undesired results when 'esc' is longer than
MAX_ESC_LEN. Please don't start proving me that this can't happen in the
current code. I still don't think that saving a few bytes is worth the
hassle.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-09-30 7:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 12:39 Ahmad Fatoum
2020-09-30 7:31 ` Sascha Hauer [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-14 9:59 Ahmad Fatoum
2020-09-28 9:31 ` Sascha Hauer
2020-09-28 11:51 ` Ahmad Fatoum
2020-09-28 11:58 ` Sascha Hauer
2020-09-28 12:40 ` Ahmad Fatoum
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=20200930073110.GF11648@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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