From: "Jiang, YuX" <yux.jiang@intel.com>
To: David Marchand <david.marchand@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
Sachin Saxena <sachin.saxena@nxp.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
"Shreyansh Jain" <shreyansh.jain@nxp.com>
Subject: RE: [PATCH 1/2] raw/skeleton: fix selftest
Date: Mon, 13 Mar 2023 02:17:17 +0000 [thread overview]
Message-ID: <BYAPR11MB2711B6B35975C8851C1FD9D9FEB99@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230310142604.2409586-1-david.marchand@redhat.com>
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Friday, March 10, 2023 10:26 PM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Sachin Saxena <sachin.saxena@nxp.com>; Hemant
> Agrawal <hemant.agrawal@nxp.com>; Shreyansh Jain
> <shreyansh.jain@nxp.com>
> Subject: [PATCH 1/2] raw/skeleton: fix selftest
>
> ASan reported issues in this driver.
>
> rte_rawdev_obj_t context object points at a uint16_t.
> skeleton_rawdev_enqueue_bufs() and skeleton_rawdev_dequeue_bufs() were
> incorrectly casting to an int.
>
> The enqueue/dequeue selftest had a leak on the enqueued string and was
> wrong in passing a rte_rawdev_buf pointer array.
> Fix this by allocating buffers on the stack and check that returned string is the
> expected one.
>
> Bugzilla ID: 1175
> Fixes: 61c592a8d035 ("raw/skeleton: introduce skeleton rawdev driver")
> Fixes: 55ca1b0f2151 ("raw/skeleton: add test cases")
> Cc: stable@dpdk.org
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
Tested-by: Yu Jiang <yux.jiang@intel.com>
Best regards,
Yu Jiang
next prev parent reply other threads:[~2023-03-13 2:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 14:26 David Marchand
2023-03-10 14:26 ` [PATCH 2/2] test: add rawdev to fast tests David Marchand
2023-03-16 8:27 ` Hemant Agrawal
2023-03-13 2:17 ` Jiang, YuX [this message]
2023-03-14 8:39 ` [PATCH 1/2] raw/skeleton: fix selftest David Marchand
2023-03-16 8:26 ` Hemant Agrawal
2023-03-16 12:51 ` 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=BYAPR11MB2711B6B35975C8851C1FD9D9FEB99@BYAPR11MB2711.namprd11.prod.outlook.com \
--to=yux.jiang@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=sachin.saxena@nxp.com \
--cc=shreyansh.jain@nxp.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).