From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 1/2] Loop block device for sandbox
Date: Wed, 5 Sep 2012 14:52:56 +0200 [thread overview]
Message-ID: <201209051452.57146.marex@denx.de> (raw)
In-Reply-To: <1644511.X2JLGWi2Ll@merom>
Dear Pavel Herrmann,
[...]
> >
> > move this out.
> >
> > besides, I think it'd be much systematic to just scream at user to call
> > "sata rescan" and bail out instead of doing it for him.
>
> i dont actually need a sata rescan, i just need to make sure i have
> dynamically allocated names, so i can safely call free() later, otherwise
> this segfaults when called before sata scan
See my previous email
> > > + /* make sure we have valid filenames */
> > > + if (!zeroed) {
> > > + init_sata(0);
> > > + zeroed = 1;
> > > + }
> > > +
> > > + switch (argc) {
> > > + case 0:
> > > + case 1:
> > > + return CMD_RET_USAGE;
> > > + case 2:
> > > + dev = simple_strtoul(argv[1], NULL, 10);
> >
> > Ok, so if I run this command and ask for device 0xb00bf33d ... will this
> > survive? Hint: it won't, rangecheck missing.
>
> hint - scan_sata does the range check in this codepath
saw it, see below. Duplication of code is not good and is error prone.
> > > + return scan_sata(dev);
> > > +
> > > + case 3:
> > > + if (!strncmp(argv[1], "inf", 3)) {
> > > + dev = simple_strtoul(argv[2], NULL, 10);
> >
> > Same here
>
> see above
>
> > > + return scan_sata(dev);
> > > + }
> > > + return CMD_RET_USAGE;
> > > + case 4:
> > > + if (!strncmp(argv[1], "load", 4)) {
> > > + dev = simple_strtoul(argv[2], NULL, 10);
> > > + if ((dev < 0) || (dev >= CONFIG_SYS_SATA_MAX_DEVICE)) {
> >
> > And here you have it ?
> >
> > Uh oh, I see, sata_scan() does it for you ... I'd say, abstract it out
> > into lightweight static inline function.
> >
> > > + printf("File index %d is out of range.\n", dev);
> > > + return -EINVAL;
> > > + }
> > > + free(filenames[dev]);
> > > + filenames[dev] = strdup(argv[3]);
> > > + init_sata(dev);
> > > + return scan_sata(dev);
> > > + }
> > > + return CMD_RET_USAGE;
> > > + }
> > > + return CMD_RET_USAGE;
> > > +}
> > > +
> > > +U_BOOT_CMD(
> > > + sata_loop, 4, 1, do_loop,
> > > + "SATA loopback",
> > > + "[info] devnum - show info about loop devnum\n"
> >
> > Make this "info" part mandatory. Than you can cut the whole argc loop
> > into simple "if argc != 2 ; then fail" . And do simple checking for the
> > first letter of the argument being either i or d .
>
> wont help, still need argc 3 or 4
Makes is simpler, you can bail out if it's not 3 or 4
> > > + "sata_loop load devnum file - load file from host FS into loop
> > > devnum"
> >
> > sata_loop is redundant above.
>
> really? how do you figure?
Run "help sata_loop" and see the result ...
>
> Pavel Herrmann
next prev parent reply other threads:[~2012-09-05 12:52 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 15:46 [U-Boot] [PATCH] Loop block device for sandbox Pavel Herrmann
2012-08-29 15:48 ` Pavel Herrmann
2012-08-29 22:18 ` Marek Vasut
2012-08-30 17:14 ` Pavel Herrmann
2012-08-30 18:45 ` Marek Vasut
2012-08-30 19:07 ` Pavel Herrmann
2012-08-30 21:53 ` Marek Vasut
2012-08-31 9:09 ` Pavel Herrmann
2012-08-31 12:57 ` Marek Vasut
2012-08-31 14:25 ` Pavel Herrmann
2012-08-31 16:02 ` Marek Vasut
2012-08-31 17:56 ` Pavel Herrmann
2012-08-31 19:02 ` Marek Vasut
2012-09-01 13:19 ` [U-Boot] [PATCH v2 1/2] " Pavel Herrmann
2012-09-01 13:19 ` [U-Boot] [PATCH 2/2] Use loop block device in sandbox board Pavel Herrmann
2012-09-01 14:20 ` Marek Vasut
2012-09-03 17:24 ` Pavel Herrmann
2012-09-03 17:23 ` [U-Boot] [PATCH v2 " Pavel Herrmann
2012-09-03 16:49 ` [U-Boot] [PATCH v2 1/2] Loop block device for sandbox Marek Vasut
2012-09-03 17:31 ` Pavel Herrmann
2012-09-03 20:20 ` Marek Vasut
2012-09-05 11:16 ` [U-Boot] [PATCH v3 " Pavel Herrmann
2012-09-05 11:16 ` [U-Boot] [PATCH v3 2/2] Use loop block device in sandbox board Pavel Herrmann
2012-09-05 11:33 ` [U-Boot] [PATCH v3 1/2] Loop block device for sandbox Marek Vasut
2012-09-05 12:38 ` Pavel Herrmann
2012-09-05 12:48 ` Marek Vasut
2012-09-05 20:25 ` Pavel Herrmann
2012-09-06 1:08 ` Marek Vasut
2012-09-06 8:45 ` Pavel Herrmann
2012-09-06 8:48 ` Marek Vasut
2012-09-05 12:42 ` Pavel Herrmann
2012-09-05 12:52 ` Marek Vasut [this message]
2012-09-06 12:31 ` [U-Boot] [PATCH v4 " Pavel Herrmann
2012-09-06 23:29 ` Marek Vasut
2012-09-07 9:19 ` Pavel Herrmann
2012-09-07 9:26 ` Marek Vasut
2012-09-07 9:38 ` Pavel Herrmann
2012-09-07 9:42 ` Marek Vasut
2012-09-13 22:31 ` Tom Rini
2012-09-16 11:49 ` Pavel Herrmann
2012-09-16 11:58 ` [U-Boot] [PATCH v5 " Pavel Herrmann
2012-09-28 9:21 ` [U-Boot] [PATCH v6 " Pavel Herrmann
2012-09-28 18:22 ` Marek Vasut
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=201209051452.57146.marex@denx.de \
--to=marex@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox