From: Peter Mamonov <pmamonov@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 1/3] lib: parse_area_spec: don't modify *start value if parse failed
Date: Wed, 17 Jan 2018 12:31:00 +0300 [thread overview]
Message-ID: <20180117093059.mjfdgy3jve4wkcon@localhost.localdomain> (raw)
In-Reply-To: <20180117081112.hir6nitsmckvdjw7@pengutronix.de>
On Wed, Jan 17, 2018 at 09:11:12AM +0100, Sascha Hauer wrote:
> On Mon, Jan 15, 2018 at 02:32:31PM +0300, Peter Mamonov wrote:
> > Signed-off-by: Peter Mamonov <pmamonov@gmail.com>
> > ---
> > lib/misc.c | 14 +++++++++-----
> > 1 file changed, 9 insertions(+), 5 deletions(-)
> >
> > diff --git a/lib/misc.c b/lib/misc.c
> > index 62ddd6677..1767043d1 100644
> > --- a/lib/misc.c
> > +++ b/lib/misc.c
> > @@ -79,19 +79,19 @@ EXPORT_SYMBOL(strtoul_suffix);
> > int parse_area_spec(const char *str, loff_t *start, loff_t *size)
> > {
> > char *endp;
> > - loff_t end;
> > + loff_t end, _start;
> >
> > if (!isdigit(*str))
> > return -1;
> >
> > - *start = strtoull_suffix(str, &endp, 0);
> > + _start = strtoull_suffix(str, &endp, 0);
> >
> > str = endp;
> >
> > if (!*str) {
> > /* beginning given, but no size, assume maximum size */
> > *size = ~0;
> > - return 0;
> > + goto success;
> > }
> >
> > if (*str == '-') {
> > @@ -102,15 +102,19 @@ int parse_area_spec(const char *str, loff_t *start, loff_t *size)
> > return -1;
> > }
> > *size = end - *start + 1;
>
> Applied with two little changes: It must be _start above and in another
> case not visible in the patch. *start is not yet initialized.
Thanks for correction. Actually these changes were present in the original
patch, but I've missed them while rearranging it.
Regards,
Peter
>
> Sascha
>
>
> --
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 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
prev parent reply other threads:[~2018-01-17 9:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 10:48 command: hashsum: md5sum reports wrong sum for the file named 4k.bin Peter Mamonov
2017-12-21 10:48 ` Peter Mamonov
2018-01-05 11:44 ` Sascha Hauer
2018-01-05 18:17 ` Peter Mamonov
2018-01-09 11:10 ` Sascha Hauer
2018-01-09 14:21 ` [PATCH] lib: parse_area_spec: don't modify *start and *size values if parse failed Peter Mamonov
2018-01-11 8:15 ` Sascha Hauer
2018-01-11 17:28 ` Peter Mamonov
2018-01-15 11:32 ` [PATCH v2 1/3] lib: parse_area_spec: don't modify *start value " Peter Mamonov
2018-01-15 11:32 ` [PATCH v2 2/3] lib: parse_area_spec: part of the area spec after -/+ should start with a digit Peter Mamonov
2018-01-15 11:32 ` [PATCH v2 3/3] lib: parse_area_spec: no extra symbols after area spec are allowed except for spaces Peter Mamonov
2018-01-17 8:11 ` [PATCH v2 1/3] lib: parse_area_spec: don't modify *start value if parse failed Sascha Hauer
2018-01-17 9:31 ` Peter Mamonov [this message]
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=20180117093059.mjfdgy3jve4wkcon@localhost.localdomain \
--to=pmamonov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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