From: Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>
To: Kevin Traynor <ktraynor@redhat.com>, dev@dpdk.org
Cc: david.marchand@redhat.com
Subject: Re: [dpdk-dev] [PATCH v2] test/eal: check invalid cpu value
Date: Mon, 20 Jul 2020 13:08:50 +0200 [thread overview]
Message-ID: <286a6f76-3047-2acc-61e3-83bdfb407535@partner.samsung.com> (raw)
In-Reply-To: <20200720101908.12500-1-ktraynor@redhat.com>
W dniu 20.07.2020 o 12:19, Kevin Traynor pisze:
> When using --lcores option, there is a limit of CPU_SETSIZE.
> Currently that allows 0..1023 on Linux.
>
> Check it is caught when this limit is exceeded.
>
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
> ---
> app/test/test_eal_flags.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/app/test/test_eal_flags.c b/app/test/test_eal_flags.c
> index 4ee809e3d..b019656b2 100644
> --- a/app/test/test_eal_flags.c
> +++ b/app/test/test_eal_flags.c
> @@ -528,4 +528,7 @@ test_missing_c_flag(void)
> "--lcores",
> "0-1,2@(5-7),(3-5)@(0,2),(0,6),7"};
> + /* check an invalid cpu value >= CPU_SETSIZE */
> + const char * const argv30[] = { prgname, prefix, mp_flag,
> + "--lcores", "3@" RTE_STR(CPU_SETSIZE) };
>
> if (launch_proc(argv2) != 0) {
> @@ -577,5 +580,5 @@ test_missing_c_flag(void)
> launch_proc(argv24) == 0 || launch_proc(argv25) == 0 ||
> launch_proc(argv26) == 0 || launch_proc(argv27) == 0 ||
> - launch_proc(argv28) == 0) {
> + launch_proc(argv28) == 0 || launch_proc(argv30) == 0) {
> printf("Error - "
> "process ran without error with invalid --lcore flag\n");
Now it's perfect.
Acked-by: Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>
--
Lukasz Wojciechowski
Principal Software Engineer
Samsung R&D Institute Poland
Samsung Electronics
Office +48 22 377 88 25
l.wojciechow@partner.samsung.com
next prev parent reply other threads:[~2020-07-20 11:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200612121031eucas1p2e5d39ccf4ebc398d4b4655fb9f5ac6e1@eucas1p2.samsung.com>
2020-06-12 12:09 ` [dpdk-dev] [PATCH] " Kevin Traynor
2020-07-08 23:04 ` Lukasz Wojciechowski
2020-07-20 10:20 ` Kevin Traynor
2020-07-20 10:17 ` Kevin Traynor
2020-07-20 10:19 ` [dpdk-dev] [PATCH v2] " Kevin Traynor
2020-07-20 11:08 ` Lukasz Wojciechowski [this message]
2020-07-21 18:58 ` David Marchand
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=286a6f76-3047-2acc-61e3-83bdfb407535@partner.samsung.com \
--to=l.wojciechow@partner.samsung.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.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;
as well as URLs for NNTP newsgroup(s).