From: Anoob Joseph <anoobj@marvell.com>
To: Volodymyr Fialko <vfialko@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Koteswara Rao Kottidi <skoteshwar@marvell.com>,
Ankur Dwivedi <adwivedi@marvell.com>,
Tejasree Kondoj <ktejasree@marvell.com>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Volodymyr Fialko <vfialko@marvell.com>,
Akhil Goyal <gakhil@marvell.com>
Subject: RE: [PATCH] crypto/cnxk: update number of max capabilities
Date: Wed, 15 Mar 2023 04:52:20 +0000 [thread overview]
Message-ID: <PH0PR18MB467248D02D6DF9802ED71385DFBF9@PH0PR18MB4672.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230314140109.3024760-1-vfialko@marvell.com>
> Subject: [PATCH] crypto/cnxk: update number of max capabilities
>
> To ensure that the end marker can fit into the capabilities array, the max
> number of capabilities has been incremented.
> Additionally, throw an error if max length is reached. It's critical because
> `rte_cryptodev_capabilities` in dev_info relies on the end marker.
> Without it, all capabilities scans will read memory outside of the array.
>
> Signed-off-by: Volodymyr Fialko <vfialko@marvell.com>
> ---
> drivers/common/cnxk/roc_platform.h | 1 +
> drivers/crypto/cnxk/cnxk_cryptodev.h | 2 +-
> .../crypto/cnxk/cnxk_cryptodev_capabilities.c | 18 +++++-------------
> 3 files changed, 7 insertions(+), 14 deletions(-)
Acked-by: Anoob Joseph <anoobj@marvell.com>
next prev parent reply other threads:[~2023-03-15 4:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 14:01 Volodymyr Fialko
2023-03-15 4:52 ` Anoob Joseph [this message]
2023-03-16 19:01 ` Akhil Goyal
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=PH0PR18MB467248D02D6DF9802ED71385DFBF9@PH0PR18MB4672.namprd18.prod.outlook.com \
--to=anoobj@marvell.com \
--cc=adwivedi@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ktejasree@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
--cc=vfialko@marvell.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).