From: zhaogongyi via ltp <ltp@lists.linux.it>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v2 1/2] lib/safe_macros: Add SAFE_STRTOF
Date: Fri, 2 Dec 2022 02:34:19 +0000 [thread overview]
Message-ID: <fb6425cf863e4c178db2cb78cee119eb@huawei.com> (raw)
Hi Cyril,
>
> Hi!
> > +float safe_strtof(const char *file, const int lineno,
> > + void (cleanup_fn) (void), char *str,
> > + float min, float max)
> > +{
> > + float rval;
> > + char *endptr;
> > +
> > + errno = 0;
> > + rval = strtof(str, &endptr);
> > +
> > + if ((errno == ERANGE) || (rval == 0)
> > + || (rval == HUGE_VAL) || (rval == -HUGE_VAL)) {
>
> This does not look right, supposedly the ERANGE is only set on overflow,
> and the rval is not guaranteed to be exact on underflow. Also rval == 0 is a
> valid result.
>
According to man 3 strtof, it seems there are some cases like:
1. strtof return the converted value as normal
2. strtof return 0 when no conversion is performed, and endptr == nptr: 'rval == 0'
3. strtof return HUGE_VAL or -HUGE_VAL when overflow: '(rval == HUGE_VAL) || (rval == -HUGE_VAL)'
4. strtof retrun 0 and set errno to ERANGE when underflow: 'errno == ERANGE'
For 2, it seems need to add checking of endptr when 'rval == 0' like: (rval == 0 && !strcmp(endptr, nptr)
Other places seem to be fine.
Regards,
Gongyi
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2022-12-02 2:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 2:34 zhaogongyi via ltp [this message]
2022-12-02 10:37 ` [LTP] [PATCH v2 1/2] lib/safe_macros: Add SAFE_STRTOF Cyril Hrubis
-- strict thread matches above, loose matches on Subject: below --
2022-12-05 7:03 zhaogongyi via ltp
2022-12-02 2:54 zhaogongyi via ltp
2022-12-01 2:51 [LTP] [PATCH v2 0/2] Add handling of abnormal input for parse_opts() Zhao Gongyi via ltp
2022-12-01 2:51 ` [LTP] [PATCH v2 1/2] lib/safe_macros: Add SAFE_STRTOF Zhao Gongyi via ltp
2022-12-01 13:42 ` Cyril Hrubis
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=fb6425cf863e4c178db2cb78cee119eb@huawei.com \
--to=ltp@lists.linux.it \
--cc=chrubis@suse.cz \
--cc=zhaogongyi@huawei.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 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.