From: David Marchand <david.marchand@redhat.com>
To: Quentin Armitage <quentin@armitage.org.uk>
Cc: dev <dev@dpdk.org>, Harman Kalra <hkalra@marvell.com>
Subject: Re: [PATCH 1/1] tap: fix write-after-free and double free of intr_handle
Date: Tue, 3 May 2022 16:30:05 +0200 [thread overview]
Message-ID: <CAJFAV8xEw55o9nLuuu5ZJvMGCpOzop=T1GaJZJB7eaS_CHNjzQ@mail.gmail.com> (raw)
In-Reply-To: <20220502192238.348172-2-quentin@armitage.org.uk>
On Mon, May 2, 2022 at 9:23 PM Quentin Armitage <quentin@armitage.org.uk> wrote:
>
> rte_pmd_tun/tap_probe() allocates pmd->intr_handle in
> eth_dev_tap_create() and it should not be freed until
> rte_pmd_tap_remove() is called.
>
> Inspection of tap_rx_intr_vec_set() shows that the call to
> tap_tx_intr_vec_uninstall() was calling rte_intr_instance_free() but
> tap_tx_intr_vec_install() can then be immediately called, and this then
> uses pmd->intr_handle without it being reallocated.
>
> This commit moves the call of rte_intr_instance_free() from
> tap_tx_intr_vec_uninstall() to rte_pmd_tap_remove().
Good catch.
We want this fix backported:
Fixes: d61138d4f0e2 ("drivers: remove direct access to interrupt handle")
Cc: stable@dpdk.org
>
> Signed-off-by: Quentin Armitage <quentin@armitage.org.uk>
> ---
> drivers/net/tap/rte_eth_tap.c | 5 +++++
> drivers/net/tap/tap_intr.c | 2 --
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/tap/rte_eth_tap.c b/drivers/net/tap/rte_eth_tap.c
> index bc3d56a311..aab1692ebf 100644
> --- a/drivers/net/tap/rte_eth_tap.c
> +++ b/drivers/net/tap/rte_eth_tap.c
> @@ -2612,14 +2612,19 @@ static int
> rte_pmd_tap_remove(struct rte_vdev_device *dev)
> {
> struct rte_eth_dev *eth_dev = NULL;
> + struct pmd_internals *pmd;
> + struct rte_intr_handle *intr_handle;
>
> /* find the ethdev entry */
> eth_dev = rte_eth_dev_allocated(rte_vdev_device_name(dev));
> if (!eth_dev)
> return 0;
>
> + pmd = eth_dev->data->dev_private;
> + intr_handle = pmd->intr_handle;
> tap_dev_close(eth_dev);
> rte_eth_dev_release_port(eth_dev);
> + rte_intr_instance_free(intr_handle);
intr_handle is shared for multiprocess, so freeing should happen in
the primary process only.
For this reason, rte_intr_instance_free() should probably go to tap_dev_close.
>
> return 0;
> }
> diff --git a/drivers/net/tap/tap_intr.c b/drivers/net/tap/tap_intr.c
> index 56c343acea..a9097def1a 100644
> --- a/drivers/net/tap/tap_intr.c
> +++ b/drivers/net/tap/tap_intr.c
> @@ -34,8 +34,6 @@ tap_rx_intr_vec_uninstall(struct rte_eth_dev *dev)
> rte_intr_free_epoll_fd(intr_handle);
> rte_intr_vec_list_free(intr_handle);
> rte_intr_nb_efd_set(intr_handle, 0);
> -
> - rte_intr_instance_free(intr_handle);
> }
>
> /**
> --
> 2.34.1
>
--
David Marchand
prev parent reply other threads:[~2022-05-03 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 19:22 [PATCH 0/1] " Quentin Armitage
2022-05-02 19:22 ` [PATCH 1/1] " Quentin Armitage
2022-05-03 14:30 ` 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='CAJFAV8xEw55o9nLuuu5ZJvMGCpOzop=T1GaJZJB7eaS_CHNjzQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=quentin@armitage.org.uk \
/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).