From: Kevin Traynor <ktraynor@redhat.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Thomas Monjalon <thomas@monjalon.net>, Ori Kam <orika@nvidia.com>
Cc: stable@dpdk.org, dev@dpdk.org,
Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
Ali Alnubani <alialnu@nvidia.com>,
benjamin.walker@intel.com,
David Christensen <drc@linux.vnet.ibm.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Ian Stokes <ian.stokes@intel.com>,
Jerin Jacob <jerinj@marvell.com>,
John McNamara <john.mcnamara@intel.com>,
Ju-Hyoung Lee <juhlee@microsoft.com>,
Luca Boccassi <bluca@debian.org>, Pei Zhang <pezhang@redhat.com>,
qian.q.xu@intel.com, Raslan Darawsheh <rasland@nvidia.com>,
yuan.peng@intel.com, zhaoyan.chen@intel.com
Subject: Re: 21.11.1 patches review and test
Date: Wed, 13 Apr 2022 11:06:24 +0100 [thread overview]
Message-ID: <42961b14-a277-8cfb-13c2-66b904015df2@redhat.com> (raw)
In-Reply-To: <CAATJJ0KpbsGCzyxdPummmhXmmyGHusgYQ34axEmGvcWsZSsXZg@mail.gmail.com>
Hi Christian/Thomas/Ori,
On 11/04/2022 07:58, Christian Ehrhardt wrote:
> On Fri, Apr 1, 2022 at 12:22 PM Kevin Traynor<ktraynor@redhat.com> wrote:
>> Hi all,
>>
>> Here is a list of patches targeted for stable release 21.11.1.
> Hi Kevin,
> this breaks on me at build time due to symbol changes.
> It is a wild mix of Base->Internal/Experimental, a few new symbols,
> and even just removed ones (in gpu which is experimental, but still
> would that need a minor soname bump?).
> They might be intentional, but it felt too much to me without at least
> discussing it.
> Could you have a look if you think that they are all intentional, save
> and correct for an LTS release?
>
Thanks for the report. I've looked through these. Comments below.
> dpkg-gensymbols: warning: some new symbols appeared in the symbols
> file: see diff output below
> dpkg-gensymbols: warning: debian/librte-common-cnxk22/DEBIAN/symbols
> doesn't match completely debian/librte-common-cnxk22.symbols
> --- debian/librte-common-cnxk22.symbols
> (librte-common-cnxk22_21.11.1~rc1-0ubuntu1~jammyppa2_amd64)
> +++ dpkg-gensymbolsUuRb8d 2022-04-11 06:46:22.276766813 +0000
> @@ -197,6 +197,7 @@
> roc_nix_ptp_clock_read@INTERNAL 21.08
> roc_nix_ptp_info_cb_register@INTERNAL 21.08
> roc_nix_ptp_info_cb_unregister@INTERNAL 21.08
> + roc_nix_ptp_is_enable@INTERNAL 21.11.1~rc1-0ubuntu1~jammyppa2
> roc_nix_ptp_rx_ena_dis@INTERNAL 21.08
> roc_nix_ptp_sync_time_adjust@INTERNAL 21.08
> roc_nix_ptp_tx_ena_dis@INTERNAL 21.08
>
This is a new internal from:
commit 28acfe550dcb12b0908df754a4307b8b4d1fe5b0
Author: Harman Kalra <hkalra@marvell.com>
Date: Thu Mar 3 12:30:42 2022 +0530
common/cnxk: fix mbuf data offset for VF
[ upstream commit 8f98e3ecc55e02234f8bec7213b0b6a69c086949 ]
Looks ok to me.
> dpkg-gensymbols: warning: some new symbols appeared in the symbols
> file: see diff output below
> dpkg-gensymbols: warning: debian/librte-ethdev22/DEBIAN/symbols
> doesn't match completely debian/librte-ethdev22.symbols
> --- debian/librte-ethdev22.symbols
> (librte-ethdev22_21.11.1~rc1-0ubuntu1~jammyppa2_amd64)
> +++ dpkg-gensymbolskEnokB 2022-04-11 06:46:25.252795157 +0000
> @@ -37,6 +37,7 @@
> rte_eth_dev_flow_ctrl_get@DPDK_22 21.11
> rte_eth_dev_flow_ctrl_set@DPDK_22 21.11
> rte_eth_dev_fw_version_get@DPDK_22 21.11
> + rte_eth_dev_get_by_name@INTERNAL 21.11.1~rc1-0ubuntu1~jammyppa2
> rte_eth_dev_get_dcb_info@DPDK_22 21.11
> rte_eth_dev_get_eeprom@DPDK_22 21.11
> rte_eth_dev_get_eeprom_length@DPDK_22 21.11
>
This is a new internal
Added by:
commit 721d0bbd1668d2a4b617a4a4de0b93dd60283d58
Author: Kumara Parameshwaran <kparameshwar@vmware.com>
Date: Mon Jan 31 20:02:33 2022 +0530
ethdev: add internal function to device struct from name
[ upstream commit 961fb4029b8c52c0e8230d34993c354d70e10e14 ]
Used by:
commit ac180f4d2662503ecd18a2e94689a229104d3d61
Author: Kumara Parameshwaran <kparameshwar@vmware.com>
Date: Mon Jan 31 20:02:34 2022 +0530
net/tap: fix to populate FDs in secondary process
[ upstream commit c36ce7099c2187926cd62cff7ebd479823554929 ]
Looks ok to me.
> dpkg-gensymbols: warning: some new symbols appeared in the symbols
> file: see diff output below
> dpkg-gensymbols: error: some symbols or patterns disappeared in the
> symbols file: see diff output below
> dpkg-gensymbols: warning: debian/librte-regexdev22/DEBIAN/symbols
> doesn't match completely debian/librte-regexdev22.symbols
> --- debian/librte-regexdev22.symbols
> (librte-regexdev22_21.11.1~rc1-0ubuntu1~jammyppa2_amd64)
> +++ dpkg-gensymbolsPD0Ygo 2022-04-11 06:46:33.368872490 +0000
> @@ -1,6 +1,8 @@
> librte_regexdev.so.22 librte-regexdev22 #MINVER#
> EXPERIMENTAL@EXPERIMENTAL 20.11
> - rte_regex_devices@Base 20.11
> + INTERNAL@INTERNAL 21.11.1~rc1-0ubuntu1~jammyppa2
> + rte_regex_devices@EXPERIMENTAL 21.11.1~rc1-0ubuntu1~jammyppa2
> rte_regexdev_attr_get@EXPERIMENTAL 20.11
> rte_regexdev_attr_set@EXPERIMENTAL 20.11
> rte_regexdev_close@EXPERIMENTAL 20.11
> @@ -8,12 +10,16 @@
> rte_regexdev_count@EXPERIMENTAL 20.11
> rte_regexdev_dump@EXPERIMENTAL 20.11
> rte_regexdev_get_dev_id@EXPERIMENTAL 20.11
> - rte_regexdev_get_device_by_name@Base 20.11
> + rte_regexdev_get_device_by_name@INTERNAL 21.11.1~rc1-0ubuntu1~jammyppa2
> rte_regexdev_info_get@EXPERIMENTAL 20.11
> - rte_regexdev_is_valid_dev@Base 20.11
> - rte_regexdev_logtype@Base 20.11
> + rte_regexdev_is_valid_dev@EXPERIMENTAL 21.11.1~rc1-0ubuntu1~jammyppa2
> + rte_regexdev_logtype@EXPERIMENTAL 21.11.1~rc1-0ubuntu1~jammyppa2
> rte_regexdev_queue_pair_setup@EXPERIMENTAL 20.11
> - rte_regexdev_register@Base 20.11
> + rte_regexdev_register@INTERNAL 21.11.1~rc1-0ubuntu1~jammyppa2
> rte_regexdev_rule_db_compile_activate@EXPERIMENTAL 20.11
> rte_regexdev_rule_db_export@EXPERIMENTAL 20.11
> rte_regexdev_rule_db_import@EXPERIMENTAL 20.11
> @@ -21,7 +27,8 @@
> rte_regexdev_selftest@EXPERIMENTAL 20.11
> rte_regexdev_start@EXPERIMENTAL 20.11
> rte_regexdev_stop@EXPERIMENTAL 20.11
> - rte_regexdev_unregister@Base 20.11
> + rte_regexdev_unregister@INTERNAL 21.11.1~rc1-0ubuntu1~jammyppa2
> rte_regexdev_xstats_by_name_get@EXPERIMENTAL 20.11
> rte_regexdev_xstats_get@EXPERIMENTAL 20.11
> rte_regexdev_xstats_names_get@EXPERIMENTAL 20.11
>
+cc Ori, regex maintainer.
Regex library is an experimental API so everything should have been
experimental or internal. This is fixing that issue.
It is fixed with
commit 6e7f8939f23c2c8ed80602bc0d62990eebe52013
Author: Thomas Monjalon <thomas@monjalon.net>
Date: Sun Mar 6 10:20:22 2022 +0100
regexdev: fix section attribute of symbols
[ upstream commit 89e290eb8ca99af9f7cfc3292d93860f8e672708 ]
and
commit 026470bafaa02cba0d46ed7b7e835262399a009a
Author: Thomas Monjalon <thomas@monjalon.net>
Date: Sun Mar 6 10:20:23 2022 +0100
build: hide local symbols in shared libraries
[ upstream commit b403498e14229ee903c8fff9baefcb72894062f3 ]
The fact that they are redesignated to correctly be
experimental/internal seems ok to me.
> dpkg-gensymbols: error: some symbols or patterns disappeared in the
> symbols file: see diff output below
> dpkg-gensymbols: warning: debian/librte-gpudev22/DEBIAN/symbols
> doesn't match completely debian/librte-gpudev22.symbols
> --- debian/librte-gpudev22.symbols
> (librte-gpudev22_21.11.1~rc1-0ubuntu1~jammyppa2_amd64)
> +++ dpkg-gensymbols4qkXdt 2022-04-11 06:46:34.552883776 +0000
> @@ -1,7 +1,7 @@
> librte_gpudev.so.22 librte-gpudev22 #MINVER#
> EXPERIMENTAL@EXPERIMENTAL 21.11
> INTERNAL@INTERNAL 21.11
> - gpu_logtype@Base 21.11
> rte_gpu_add_child@EXPERIMENTAL 21.11
> rte_gpu_allocate@INTERNAL 21.11
> rte_gpu_attach@INTERNAL 21.11
>
The missing wildcard meant this symbol escaped in 21.11.
It is fixed by:
commit 026470bafaa02cba0d46ed7b7e835262399a009a
Author: Thomas Monjalon <thomas@monjalon.net>
Date: Sun Mar 6 10:20:23 2022 +0100
build: hide local symbols in shared libraries
[ upstream commit b403498e14229ee903c8fff9baefcb72894062f3 ]
In this case the symbol is not redesignated but removed, but it doesn't
look to have any use to a user, so I think it can be safe to remove.
There are updates to the libabigail.ignore for regex and gpu_dev to
ignore ABI changes for these fixes.
--
I'm ok with changes above for 21.11.1, what do others think?
Kevin.
>
> Full log:
> https://launchpadlibrarian.net/596047842/buildlog_ubuntu-jammy-amd64.dpdk_21.11.1~rc1-0ubuntu1~jammyppa2_BUILDING.txt.gz
>
next prev parent reply other threads:[~2022-04-13 10:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 10:22 Kevin Traynor
2022-04-11 3:03 ` Pei Zhang
2022-04-13 4:06 ` YangHang Liu
2022-04-13 13:20 ` Kevin Traynor
2022-04-11 6:58 ` Christian Ehrhardt
2022-04-13 7:26 ` Christian Ehrhardt
2022-04-13 8:44 ` Kevin Traynor
2022-04-13 10:06 ` Kevin Traynor [this message]
2022-04-14 5:52 ` Christian Ehrhardt
2022-04-14 7:17 ` Thomas Monjalon
2022-04-14 9:08 ` Kevin Traynor
2022-04-11 11:00 ` Ali Alnubani
2022-04-13 13:18 ` Kevin Traynor
2022-04-12 8:58 ` Jiang, YuX
2022-04-13 13:19 ` Kevin Traynor
2022-04-14 4:58 ` Jiang, YuX
2022-04-25 15:01 ` Kevin Traynor
2022-04-20 5:50 ` Christian Ehrhardt
2022-04-25 13:39 ` Kevin Traynor
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=42961b14-a277-8cfb-13c2-66b904015df2@redhat.com \
--to=ktraynor@redhat.com \
--cc=Abhishek.Marathe@microsoft.com \
--cc=alialnu@nvidia.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=hemant.agrawal@nxp.com \
--cc=ian.stokes@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=juhlee@microsoft.com \
--cc=orika@nvidia.com \
--cc=pezhang@redhat.com \
--cc=qian.q.xu@intel.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yuan.peng@intel.com \
--cc=zhaoyan.chen@intel.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).