patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Thomas Monjalon <thomas@monjalon.net>, stable@dpdk.org
Cc: Matan Azrad <matan@mellanox.com>,
	Shahaf Shuler <shahafs@mellanox.com>,
	 Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Subject: Re: [dpdk-stable] [PATCH 19.11] net/mlx5: fix build with separate glue lib for dlopen
Date: Mon, 08 Jun 2020 08:59:09 +0100	[thread overview]
Message-ID: <47e5b78014f365e8ace8ce001079915a51b91b90.camel@debian.org> (raw)
In-Reply-To: <20200606100856.2073664-1-thomas@monjalon.net>

On Sat, 2020-06-06 at 12:08 +0200, Thomas Monjalon wrote:
> If building with option RTE_IBVERBS_LINK_DLOPEN (make)
> or ibverbs_link=dlopen (meson), the glue is a separate library
> which can be dlopen.
> In such case, the object mlx5_glue must be allocated in two places:
> one in the glue, and one outside of the glue to be assigned when
> loading the glue with dlopen/dlsym.
> 
> When backporting the allocation split for gcc 10, both allocations
> were made inside the glue. As a consequence, the symbol is undefined
> outside of the glue:
> 	drivers/net/mlx5/mlx5.c: undefined reference to 'mlx5_glue'
> 
> The second allocation is restored outside of the glue, in mlx5.c.
> 
> Fixes: b3e01cd3e46f ("common/mlx5: fix build with -fno-common")
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
>  drivers/net/mlx5/mlx5.c      | 4 ++++
>  drivers/net/mlx5/mlx5_glue.c | 4 ----
>  2 files changed, 4 insertions(+), 4 deletions(-)

Acked-by: Luca Boccassi <bluca@debian.org>

Thanks for the fix, applied

-- 
Kind regards,
Luca Boccassi

      reply	other threads:[~2020-06-08  7:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-06 10:08 Thomas Monjalon
2020-06-08  7:59 ` Luca Boccassi [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=47e5b78014f365e8ace8ce001079915a51b91b90.camel@debian.org \
    --to=bluca@debian.org \
    --cc=matan@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@mellanox.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).