From: David Laight <David.Laight@ACULAB.COM>
To: 'Sergey Shtylyov' <s.shtylyov@omp.ru>,
Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: RE: [PATCH 1/2] usb: host: uhci-debug: use scnprintf() instead of sprintf()
Date: Sat, 12 Mar 2022 22:33:50 +0000 [thread overview]
Message-ID: <5e5c26cde6814a56a00019d81d23f386@AcuMS.aculab.com> (raw)
In-Reply-To: <20220312202834.11700-2-s.shtylyov@omp.ru>
From: Sergey Shtylyov
> Sent: 12 March 2022 20:29
>
> The UHCI driver's debugging code uses a lot of sprintf() calls with the
> large buffers, leaving some space at the end of the buffers to handle the
> buffer overflow. Using scnprntf() instead eliminates the very possibility
> of the buffer overflow, while simplifying the code at the expense of not
> printing an ellipsis when the end of buffer is actually reached...
Hmmm...
The old code seems to so:
> - out += sprintf(out, "(buf=%08x)\n", hc32_to_cpu(uhci, td->buffer));
>
> - if (out - buf > len)
> - out += sprintf(out, " ...\n");
Which is going to overflow the output buffer unless there
is enough 'tailroom' after buf[len] for all the sprintf()
before any length check and the ellipsis.
The new code won't overrun buf[len] but also fails to
'\n' terminate long lines.
So you probably do need a check for:
if (out == len - 1 && buf[out - 1] != '\n')
strcpy(buf + len - 5, "...\n");
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2022-03-12 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 20:28 [PATCH 0/2] Switch to using scnprintf() in the UHCI driver's debugging code Sergey Shtylyov
2022-03-12 20:28 ` [PATCH 1/2] usb: host: uhci-debug: use scnprintf() instead of sprintf() Sergey Shtylyov
2022-03-12 22:33 ` David Laight [this message]
2022-04-24 15:31 ` Sergey Shtylyov
2022-03-12 20:28 ` [PATCH 2/2] usb: host: uhci: remove #define EXTRA_SPACE Sergey Shtylyov
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=5e5c26cde6814a56a00019d81d23f386@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=s.shtylyov@omp.ru \
--cc=stern@rowland.harvard.edu \
/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.