From: Thomas Monjalon <thomas@monjalon.net>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: dev@dpdk.org, david.marchand@redhat.com, stable@dpdk.org,
Ray Kinsella <mdr@ashroe.eu>, Parav Pandit <parav@nvidia.com>,
Xueming Li <xuemingl@nvidia.com>,
Elena Agostini <eagostini@nvidia.com>, Ori Kam <orika@nvidia.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Michael Baum <michaelba@nvidia.com>
Subject: Re: [PATCH v2 2/2] build: hide local symbols in shared libraries
Date: Wed, 09 Mar 2022 19:54:19 +0100 [thread overview]
Message-ID: <3916698.Zkmt1EvEu4@thomas> (raw)
In-Reply-To: <0e4927c4-53ae-23a6-1fb5-fa5bd8a35d83@redhat.com>
09/03/2022 11:58, Kevin Traynor:
> Hi Thomas,
>
> On 08/03/2022 14:24, Thomas Monjalon wrote:
> > The symbols which are not listed in the version script
> > are exported by default.
> > Adding a local section with a wildcard make non-listed functions
> > and variables as hidden, as it should be in all version.map files.
> >
> > These are the changes done in the shared libraries:
> > - DF .text Base auxiliary_add_device
> > - DF .text Base auxiliary_dev_exists
> > - DF .text Base auxiliary_dev_iterate
> > - DF .text Base auxiliary_insert_device
> > - DF .text Base auxiliary_is_ignored_device
> > - DF .text Base auxiliary_match
> > - DF .text Base auxiliary_on_scan
> > - DF .text Base auxiliary_scan
> > - DO .bss Base auxiliary_bus_logtype
> > - DO .data Base auxiliary_bus
> > - DO .bss Base gpu_logtype
> >
> > There is no impact on regexdev library.
> >
> > Because these local symbols were exported as non-internal
> > in DPDK 21.11, any change in these functions would break the ABI.
> > Exception rules are added for these experimental libraries,
> > so the ABI check will skip them until the next ABI version.
> >
> > A check is added to avoid such miss in future.
> >
> > Fixes: 1afce3086cf4 ("bus/auxiliary: introduce auxiliary bus")
> > Fixes: 8b8036a66e3d ("gpudev: introduce GPU device class library")
> > Cc: stable@dpdk.org
> >
>
> If I take this 2/2 for 21.11.1, then I also need to backport [0] so I
> won't have errors for common_mlx5.
>
> Any problem with taking both?
>
> [0]
> commit c2e3059a10f2389b791d5d485fe71e666984c193
> Author: Michael Baum <michaelba@nvidia.com>
> Date: Fri Feb 25 01:25:06 2022 +0200
>
> common/mlx5: consider local functions as internal
I think that's fine to backport this as well.
next prev parent reply other threads:[~2022-03-09 18:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 9:20 [PATCH 0/2] add missing local symbols catch-all Thomas Monjalon
2022-03-06 9:20 ` [PATCH 1/2] regexdev: fix section attribute of symbols Thomas Monjalon
2022-03-07 10:15 ` Ori Kam
2022-03-06 9:20 ` [PATCH 2/2] build: hide local symbols in shared libraries Thomas Monjalon
2022-03-07 13:14 ` [PATCH 0/2] add missing local symbols catch-all David Marchand
2022-03-08 14:24 ` [PATCH v2 " Thomas Monjalon
2022-03-08 14:24 ` [PATCH v2 1/2] regexdev: fix section attribute of symbols Thomas Monjalon
2022-03-08 14:24 ` [PATCH v2 2/2] build: hide local symbols in shared libraries Thomas Monjalon
2022-03-09 10:58 ` Kevin Traynor
2022-03-09 18:54 ` Thomas Monjalon [this message]
2022-04-15 14:56 ` Ray Kinsella
2022-03-08 14:31 ` [PATCH v2 0/2] add missing local symbols catch-all Thomas Monjalon
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=3916698.Zkmt1EvEu4@thomas \
--to=thomas@monjalon.net \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=eagostini@nvidia.com \
--cc=ktraynor@redhat.com \
--cc=mdr@ashroe.eu \
--cc=michaelba@nvidia.com \
--cc=orika@nvidia.com \
--cc=parav@nvidia.com \
--cc=stable@dpdk.org \
--cc=xuemingl@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.