From: Jerin Jacob <jerinj@marvell.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>,
"david.marchand@redhat.com" <david.marchand@redhat.com>
Cc: "stephen@networkplumber.org" <stephen@networkplumber.org>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [EXTERNAL] [PATCH v2 2/3] examples/l2fwd-event: fix spinlock handling
Date: Mon, 18 Nov 2024 09:32:36 +0000 [thread overview]
Message-ID: <BY3PR18MB478540CC8C5FB4D21485493FC8272@BY3PR18MB4785.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20241114074437.2943885-2-hemant.agrawal@nxp.com>
> -----Original Message-----
> From: Hemant Agrawal <hemant.agrawal@nxp.com>
> Sent: Thursday, November 14, 2024 1:15 PM
> To: thomas@monjalon.net; dev@dpdk.org; david.marchand@redhat.com
> Cc: stephen@networkplumber.org; Pavan Nikhilesh Bhagavatula
> <pbhagavatula@marvell.com>; stable@dpdk.org
> Subject: [EXTERNAL] [PATCH v2 2/3] examples/l2fwd-event: fix spinlock
> handling
>
> Detected by pvs-studio Bug 89-93: very suspicious synchronization The analyzer
> issued a pack of V1020 warnings that a resource might remain blocked. Fixes:
> 080f57bceca4 ("examples/l2fwd-event: add eventdev main loop") Cc:
> pbhagavatula@ marvell. com
> Detected by pvs-studio
> Bug 89-93: very suspicious synchronization The analyzer issued a pack of V1020
> warnings that a resource might remain blocked.
>
> Fixes: 080f57bceca4 ("examples/l2fwd-event: add eventdev main loop")
> Cc: pbhagavatula@marvell.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
1/3 and 3/3 are NOT eventdev patches. So I Applied 2/3 to dpdk-next-eventdev/for-main and delegated 1/3 and 3/3 to Thomas.
> ---
> examples/l2fwd-event/l2fwd_event.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/examples/l2fwd-event/l2fwd_event.c b/examples/l2fwd-
> event/l2fwd_event.c
> index 22472027b9..416957384b 100644
> --- a/examples/l2fwd-event/l2fwd_event.c
> +++ b/examples/l2fwd-event/l2fwd_event.c
> @@ -141,6 +141,7 @@ l2fwd_get_free_event_port(struct
> l2fwd_event_resources *evt_rsrc)
> rte_spinlock_lock(&evt_rsrc->evp.lock);
> if (index >= evt_rsrc->evp.nb_ports) {
> printf("No free event port is available\n");
> + rte_spinlock_unlock(&evt_rsrc->evp.lock);
> return -1;
> }
>
> --
> 2.25.1
next prev parent reply other threads:[~2024-11-18 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 16:14 [PATCH 1/2] bus/dpaa: fix lock condition during error handling Hemant Agrawal
2024-11-13 16:14 ` [PATCH 2/2] examples/l2fwd-event: fix spinlock handling Hemant Agrawal
2024-11-13 16:48 ` [PATCH 1/2] bus/dpaa: fix lock condition during error handling David Marchand
2024-11-14 7:45 ` Hemant Agrawal
2024-11-14 7:44 ` [PATCH v2 1/3] " Hemant Agrawal
2024-11-14 7:44 ` [PATCH v2 2/3] examples/l2fwd-event: fix spinlock handling Hemant Agrawal
2024-11-18 9:32 ` Jerin Jacob [this message]
2024-11-14 7:44 ` [PATCH v2 3/3] bus/dpaa: enabling clang thread safety for locks Hemant Agrawal
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=BY3PR18MB478540CC8C5FB4D21485493FC8272@BY3PR18MB4785.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=pbhagavatula@marvell.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).