From: Jerin Jacob <jerinjacobk@gmail.com>
To: Pavan Nikhilesh <pbhagavatula@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>, dpdk-dev <dev@dpdk.org>,
dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] app/eventdev: fix lcore parsing skipping last core
Date: Sun, 9 May 2021 21:33:23 +0530 [thread overview]
Message-ID: <CALBAE1O9+0U34KVVeGa-sPVYwKFygDGpGUVqyc8vgkp+ju5NXQ@mail.gmail.com> (raw)
In-Reply-To: <20210506210310.308-1-pbhagavatula@marvell.com>
On Fri, May 7, 2021 at 2:33 AM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> The last lcore declared in the list is also a valid lcore in the list.
>
> Fixes: 32d7dbf269be ("app/eventdev: fix overflow in lcore list parsing")
> Cc: stable@dpdk.org
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied to dpdk-next-eventdev/for-main. Thanks.
> ---
> app/test-eventdev/parser.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/app/test-eventdev/parser.c b/app/test-eventdev/parser.c
> index 7a973cbb23..8818c37ff8 100644
> --- a/app/test-eventdev/parser.c
> +++ b/app/test-eventdev/parser.c
> @@ -345,7 +345,7 @@ parse_lcores_list(bool lcores[], int lcores_num, const char *corelist)
> max = idx;
> if (min == RTE_MAX_LCORE)
> min = idx;
> - for (idx = min; idx < max; idx++) {
> + for (idx = min; idx <= max; idx++) {
> if (lcores[idx] == 1)
> return -E2BIG;
> lcores[idx] = 1;
> --
> 2.17.1
>
prev parent reply other threads:[~2021-05-09 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 21:03 pbhagavatula
2021-05-09 16:03 ` Jerin Jacob [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=CALBAE1O9+0U34KVVeGa-sPVYwKFygDGpGUVqyc8vgkp+ju5NXQ@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=stable@dpdk.org \
/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).