From: David Marchand <david.marchand@redhat.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>,
Shahaf Shuler <shahafs@mellanox.com>
Cc: dev <dev@dpdk.org>,
"Damjan Marion (damarion)" <damarion@cisco.com>,
Thomas Monjalon <thomas@monjalon.net>,
Dariusz Stojaczyk <dariuszx.stojaczyk@intel.com>,
dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] vfio: fix getting default container
Date: Wed, 6 Nov 2019 14:44:19 +0100 [thread overview]
Message-ID: <CAJFAV8wr0T+-S5sO9_a+9u4mDwPjdCOeVcMGBxHXRH8rK=uBDQ@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8yevu9Z3piNsrQrA_tdahHcoYg0Z44WiXb_zWXniBCHew@mail.gmail.com>
On Mon, Nov 4, 2019 at 8:35 PM David Marchand <david.marchand@redhat.com> wrote:
>
> On Mon, Nov 4, 2019 at 6:41 PM Anatoly Burakov
> <anatoly.burakov@intel.com> wrote:
> >
> > When requesting DMA mapping to default container, we are meant to
> > supply the RTE_VFIO_DEFAULT_CONTAINER_FD value, however this is
> > not handled correctly by get_vfio_cfg_by_container_fd(), because
> > it only looks at actual fd values and does not check for this
> > special case.
> >
> > Fix it to return default container if the fd requested is the
> > special RTE_VFIO_DEFAULT_CONTAINER_FD value.
> >
Fixes: 4106d89a18f8 ("vfio: allow DMA map to the default container")
Cc: stable@dpdk.org
> > Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> Reviewed-by: David Marchand <david.marchand@redhat.com>
Acked-by: Shahaf Shuler <shahafs@mellanox.com>
Applied with title "vfio: fix DMA mapping with default container" as
discussed on irc.
Thanks.
--
David Marchand
prev parent reply other threads:[~2019-11-06 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 17:41 Anatoly Burakov
2019-11-04 19:35 ` David Marchand
2019-11-05 12:38 ` Shahaf Shuler
2019-11-06 13:44 ` David Marchand [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='CAJFAV8wr0T+-S5sO9_a+9u4mDwPjdCOeVcMGBxHXRH8rK=uBDQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=damarion@cisco.com \
--cc=dariuszx.stojaczyk@intel.com \
--cc=dev@dpdk.org \
--cc=shahafs@mellanox.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).