From: Steven Rostedt <rostedt@goodmis.org>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: <pmladek@suse.com>, <sergey.senozhatsky@gmail.com>,
<linux-kernel@vger.kernel.org>, <patches@opensource.cirrus.com>
Subject: Re: [PATCH] lib: vsprintf: Avoid 32-bit truncation in vsscanf number parsing
Date: Thu, 12 Nov 2020 12:04:27 -0500 [thread overview]
Message-ID: <20201112120427.72c0a237@gandalf.local.home> (raw)
In-Reply-To: <b200a554-be81-f8b0-28a4-39c6f3c6900f@opensource.cirrus.com>
On Thu, 12 Nov 2020 15:46:46 +0000
Richard Fitzgerald <rf@opensource.cirrus.com> wrote:
> See this thread from 2014 where the field width problem was raised and
> explained:
> http://lkml.iu.edu/hypermail/linux/kernel/1401.1/03443.html
>
> and the reply from Linus Torvalds that was against fixing field width
> handling:
> http://lkml.iu.edu/hypermail/linux/kernel/1401.1/03488.html
Thanks for the pointers, but note, that references to older emails should
use https://lore.kernel.org/ as these links format the output really
horribly.
>
> which I assume is why the field handling wasn't unoptimized to be
> strictly correct.
>
> Nevertheless, I see no reason not to remove avoidable inconsistencies
> from the current design.
Yes, but perhaps its time to fix the real problem and not just add
band-aids. That thread is over 6 years old (the email was from Jan 14, 2014)
$ git diff `git rev-list --before 'Jan 14 2014' HEAD --max-count=1` |
grep '^+' | grep sscanf | wc -l
622
There's been over 600 new additions of sscanf(). Now is the time to just
fix it correctly.
-- Steve
next prev parent reply other threads:[~2020-11-12 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 11:17 Richard Fitzgerald
2020-11-12 15:35 ` Steven Rostedt
2020-11-12 15:46 ` Richard Fitzgerald
2020-11-12 17:04 ` Steven Rostedt [this message]
2020-11-13 14:00 ` Petr Mladek
2020-11-16 10:47 ` Richard Fitzgerald
2020-11-12 16:17 ` Petr Mladek
2020-11-12 16:45 ` David Laight
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=20201112120427.72c0a237@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=pmladek@suse.com \
--cc=rf@opensource.cirrus.com \
--cc=sergey.senozhatsky@gmail.com \
/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
all inboxes | Powered by JetHome®