public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
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 2/2] lib: Replace atoi/atof with SAFE_STRTOL/SAFE_STRTOF
Date: Thu, 1 Dec 2022 02:59:20 +0000	[thread overview]
Message-ID: <92f26cd27f14427db5853e3d2f497050@huawei.com> (raw)

Hi Cyril,

> 
> On Wed, Nov 30, 2022 at 10:19:01AM +0800, Zhao Gongyi via ltp wrote:
> > Replace atoi/atof with SAFE_STRTOL/SAFE_STRTOF in parse_opts(), it is
> > hoped to deal with the abnormal input.
> >
> > Modify the requirement iterations range from '>= 0' to '> 0', when
> > iterations' value equal to 0, the test will not run.
> >
> > Signed-off-by: Zhao Gongyi <zhaogongyi@huawei.com>
> > ---
> >  lib/tst_test.c | 8 +++-----
> >  1 file changed, 3 insertions(+), 5 deletions(-)
> >
> > diff --git a/lib/tst_test.c b/lib/tst_test.c index
> > b62559d75..254229d96 100644
> > --- a/lib/tst_test.c
> > +++ b/lib/tst_test.c
> > @@ -677,15 +677,13 @@ static void parse_opts(int argc, char *argv[])
> >  			print_test_tags();
> >  			exit(0);
> >  		case 'i':
> > -			iterations = atoi(optarg);
> > -			if (iterations < 0)
> > -				tst_brk(TBROK, "Number of iterations (-i) must be >=
> 0");
> > +			iterations = SAFE_STRTOL(optarg, 1, INT_MAX);
> >  		break;
> >  		case 'I':
> >  			if (tst_test->max_runtime > 0)
> > -				tst_test->max_runtime = atoi(optarg);
> > +				tst_test->max_runtime = SAFE_STRTOL(optarg, 1,
> INT_MAX);
> >  			else
> > -				duration = atof(optarg);
> > +				duration = SAFE_STRTOF(optarg);
> 
> Shouldn't we limit the duration to positive numbers here as well?
> 
> I guess that we should add min and max option to the SAFE_STRTOF() and
> call the conversion with SAFE_STRTOF(optarg, 0.1, HUGE_VALF); here
> instead.

Agree, it is better to add range checking for SAFE_STRTOF, I have resubmit a new patch to fix it, please see: https://patchwork.ozlabs.org/project/ltp/patch/20221201025141.71227-3-zhaogongyi@huawei.com/

Regards,
Gongyi


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

             reply	other threads:[~2022-12-01  2:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01  2:59 zhaogongyi via ltp [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-30  2:18 [LTP] [PATCH 0/2] Add handling of abnormal input for parse_opts() Zhao Gongyi via ltp
2022-11-30  2:19 ` [LTP] [PATCH 2/2] lib: Replace atoi/atof with SAFE_STRTOL/SAFE_STRTOF Zhao Gongyi via ltp
2022-11-30 13:49   ` 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=92f26cd27f14427db5853e3d2f497050@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox