All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] fs/fs.c - error handling needed?
Date: Mon, 7 Oct 2013 08:12:52 -0400	[thread overview]
Message-ID: <20131007121252.GS15917@bill-the-cat> (raw)
In-Reply-To: <20131005194941.1BCEF380A3C@gemini.denx.de>

On Sat, Oct 05, 2013 at 09:49:41PM +0200, Wolfgang Denk wrote:
> Dear Simon,
> 
> with commit a8f6ab5 "fs: Add support for saving data to filesystems"
> you add the function do_save() to U-Boot.  This includes the following
> code (line numbers as of current master):
> 
> "fs/fs.c":
> 
> ...
> 331         filename = argv[3];
> 332         addr = simple_strtoul(argv[4], NULL, cmdline_base);
> 333         bytes = simple_strtoul(argv[5], NULL, cmdline_base);
> 334         if (argc >= 7)
> 335                 pos = simple_strtoul(argv[6], NULL, cmdline_base);
> 336         else
> 337                 pos = 0;
> 
> 
> Should we not perform at least minimal error checking, i. e. verify
> that no garbage arguments have been passed to that function?

Yes, we ought to.  If you don't pass fatwrite the right number of
arguments we get data aborts, for example.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20131007/4f2469a8/attachment.pgp>

  reply	other threads:[~2013-10-07 12:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-05 19:49 [U-Boot] fs/fs.c - error handling needed? Wolfgang Denk
2013-10-07 12:12 ` Tom Rini [this message]
2013-10-07 13:55   ` Wolfgang Denk
2013-10-07 14:23     ` Tom Rini
2013-10-08 16:58 ` Simon Glass

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=20131007121252.GS15917@bill-the-cat \
    --to=trini@ti.com \
    --cc=u-boot@lists.denx.de \
    /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.