From: Raslan Darawsheh <rasland@nvidia.com>
To: Shiri Kuzin <shirik@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>, Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH] common/mlx5: fix mkey attributes initialization
Date: Sun, 9 May 2021 08:21:48 +0000 [thread overview]
Message-ID: <DM6PR12MB2748C622F96A59F21D39EB8FCF559@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210507070122.174449-1-shirik@nvidia.com>
Hi,
> -----Original Message-----
> From: Shiri Kuzin <shirik@nvidia.com>
> Sent: Friday, May 7, 2021 10:01 AM
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; Raslan Darawsheh
> <rasland@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>
> Subject: [PATCH] common/mlx5: fix mkey attributes initialization
>
> The crypto driver added new fields to the mkey attributes struct:
> crypto_en and set_remote_rw.
>
> The entire mkey struct was not initialized, only specific fields in it,
> which caused the new added fields not to be initialized resulting in a
> mkey creation error.
>
> This is fixed by initializing the entire mkey attributes struct to 0
> which will prevent this issue from reoccurring if any fields are added
> to the mkey sturct in the future.
>
> Fixes: 0111a74e13dd ("common/mlx5: adjust DevX mkey fields for crypto")
>
> Signed-off-by: Shiri Kuzin <shirik@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
> ---
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2021-05-09 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 7:01 Shiri Kuzin
2021-05-09 8:21 ` Raslan Darawsheh [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=DM6PR12MB2748C622F96A59F21D39EB8FCF559@DM6PR12MB2748.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=shirik@nvidia.com \
--cc=viacheslavo@nvidia.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).