From: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
To: Ciara Power <ciara.power@intel.com>, dev@dpdk.org
Cc: gakhil@marvell.com, olivier.matz@6wind.com, stable@dpdk.org,
"Morten Brørup" <mb@smartsharesystems.com>,
"Kai Ji" <kai.ji@intel.com>, "Fan Zhang" <fanzhang.oss@gmail.com>
Subject: Re: [PATCH v2] cryptodev: fix device socket ID type
Date: Wed, 5 Jul 2023 12:29:16 +0100 [thread overview]
Message-ID: <fc79543c-e4ed-ca8b-9cde-a691306861a1@yandex.ru> (raw)
In-Reply-To: <20230705103630.1131136-1-ciara.power@intel.com>
05/07/2023 11:36, Ciara Power пишет:
> The socket ID field for a cryptodev device data was unsigned int.
> Due to recent changes to the default device socket ID,
> this caused an issue when the socket ID was unknown and set to -1.
> The device socket ID wrapped around to 255,
> and caused errors when allocating memory.
>
> Changing this field type to int fixes the issue, as it now takes the
> correct -1 value.
>
> Fixes: 7dcd73e37965 ("drivers/bus: set device NUMA node to unknown by default")
> Cc: olivier.matz@6wind.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Ciara Power <ciara.power@intel.com>
> Acked-by: Morten Brørup <mb@smartsharesystems.com>
> Acked-by: Kai Ji <kai.ji@intel.com>
>
> ---
> v2: Added cc for stable mailing list
> ---
> lib/cryptodev/cryptodev_pmd.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/cryptodev/cryptodev_pmd.h b/lib/cryptodev/cryptodev_pmd.h
> index 8710ed7558..4c98cedca6 100644
> --- a/lib/cryptodev/cryptodev_pmd.h
> +++ b/lib/cryptodev/cryptodev_pmd.h
> @@ -65,7 +65,7 @@ struct rte_cryptodev_data {
> /** Device ID for this instance */
> uint8_t dev_id;
> /** Socket ID where memory is allocated */
> - uint8_t socket_id;
> + int socket_id;
> /** Unique identifier name */
> char name[RTE_CRYPTODEV_NAME_MAX_LEN];
>
Acked-by: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
next prev parent reply other threads:[~2023-07-05 11:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230629132155.75075-1-ciara.power@intel.com>
2023-07-05 10:36 ` Ciara Power
2023-07-05 11:29 ` Konstantin Ananyev [this message]
2023-07-05 18:23 ` [EXT] " 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=fc79543c-e4ed-ca8b-9cde-a691306861a1@yandex.ru \
--to=konstantin.v.ananyev@yandex.ru \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@marvell.com \
--cc=kai.ji@intel.com \
--cc=mb@smartsharesystems.com \
--cc=olivier.matz@6wind.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).