From: Akhil Goyal <gakhil@marvell.com>
To: Michael Baum <michaelba@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>,
Raslan Darawsheh <rasland@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [EXT] [PATCH] compress/mlx5: fix memory region unregistration
Date: Wed, 7 Jul 2021 19:06:58 +0000 [thread overview]
Message-ID: <CO6PR18MB44844F47958867B2D29E930AD81A9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210701071807.2018505-1-michaelba@nvidia.com>
> The issue can cause illegal physical address access while a huge-page A
> is released and huge-page B is allocated on the same virtual address.
> The old MR can be matched using the virtual address of huge-page B but
> the HW will access the physical address of huge-page A which is no more
> part of the DPDK process.
>
> Register a driver callback for memory event in order to free out all the
> MRs of memory that is going to be freed from the dpdk process.
>
> Fixes: f8c97babc9f4 ("compress/mlx5: add data-path functions")
> Cc: stable@dpdk.org
>
> Signed-off-by: Michael Baum <michaelba@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
> ---
CI is reporting error with this patch. Can you check?
next prev parent reply other threads:[~2021-07-07 19:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 7:18 [dpdk-dev] " Michael Baum
2021-07-07 19:06 ` Akhil Goyal [this message]
2021-07-08 6:25 ` [dpdk-dev] [EXT] " Michael Baum
2021-07-09 15:56 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2021-07-12 7:19 ` [dpdk-dev] [PATCH v2] " Michael Baum
2021-07-18 9:39 ` [dpdk-dev] [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=CO6PR18MB44844F47958867B2D29E930AD81A9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=michaelba@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--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).