From: Jerin Jacob <jerinj@marvell.com>
To: Luka Jankovic <luka.jankovic@ericsson.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXTERNAL] [PATCH] eventdev: fix dereferencing null atomic locks pointer in test-eventdev
Date: Tue, 1 Apr 2025 09:00:27 +0000 [thread overview]
Message-ID: <BY3PR18MB4785DFD4760032CCB055DA6AC8AC2@BY3PR18MB4785.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250326100952.114143-1-luka.jankovic@ericsson.com>
> -----Original Message-----
> From: Luka Jankovic <luka.jankovic@ericsson.com>
> Sent: Wednesday, March 26, 2025 3:40 PM
> To: luka.jankovic@ericsson.com
> Cc: Jerin Jacob <jerinj@marvell.com>; dev@dpdk.org
> Subject: [EXTERNAL] [PATCH] eventdev: fix dereferencing null atomic locks
> pointer in test-eventdev
>
> Update atomic_init_locks to immediately return if memory allocation fails.
> Atomic queue and atq tests updated to handle atomic locks being null. Coverity
> issue: 457876 Fixes: 9d619f82321b ("app/eventdev: introduce atomic tests")
> Signed-off-by:
> Update atomic_init_locks to immediately return if memory allocation fails.
> Atomic queue and atq tests updated to handle atomic locks being null.
>
> Coverity issue: 457876
> Fixes: 9d619f82321b ("app/eventdev: introduce atomic tests")
>
> Signed-off-by: Luka Jankovic <luka.jankovic@ericsson.com>
Please check the git history of the file to know the starting tag.
Updated the git commit as follows and applied to dpdk-next-net-eventdev/for-main. Thanks
app/eventdev: fix dereferencing null
Update atomic_init_locks to immediately return if memory allocation
fails.
Atomic queue and ATQ tests updated to handle atomic locks being NULL
Coverity issue: 457876
Fixes: 9d619f82321b ("app/eventdev: introduce atomic tests")
Cc: stable@dpdk.org
Signed-off-by: Luka Jankovic <luka.jankovic@ericsson.com>
prev parent reply other threads:[~2025-04-01 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 10:09 Luka Jankovic
2025-04-01 9:00 ` 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=BY3PR18MB4785DFD4760032CCB055DA6AC8AC2@BY3PR18MB4785.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=luka.jankovic@ericsson.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).