From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Benjamin Drung
<benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>,
List Linux RDMA Mailing
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: rdma-core: libibumad symbols version downgrade
Date: Wed, 19 Apr 2017 09:36:56 -0600 [thread overview]
Message-ID: <20170419153656.GB29293@obsidianresearch.com> (raw)
In-Reply-To: <20170419100430.GI14088-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
On Wed, Apr 19, 2017 at 01:04:30PM +0300, Leon Romanovsky wrote:
> On Tue, Apr 18, 2017 at 07:55:11PM +0200, Benjamin Drung wrote:
> > Hi,
> >
> > while reviewing the Debian packaging changes from libibumad
> > 1.3.10.2-2 to rdma-core, I stumbled over the symbols version.
> > libibumad 1.3.10.2 ships libibumad.so.3.1.0, but rdma-core
> > ships libibumad.so.3.0.14 which is lower. Is that intentional?
It was intentional:
commit 232796a623f28bd205d15acac44bb007b8fc64be
Author: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Date: Mon Jan 30 11:04:21 2017 -0700
Fix shared library filenames
We expect the filename to reflect the symbol versions in the file,
this means, eg libibverbs1.3 should have the IBVERBS_1.3 as the newest
symbol. The same applies to all libraries.
verbs was not updated in commit 3ca7a103148 when new symbols were added
umad/rdmacm probably legitimately had a '.1' someday, but failed to
follow symver convention. Bump it back down.
Since distros are not using it in packaging the shared library version
and filename is no longer used by anything. We simply want it to follow
our own internal conventions.
Fixes: 3ca7a1031486 ("ibverbs: Add support for packet pacing")
Signed-off-by: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-04-19 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 17:55 rdma-core: libibumad symbols version downgrade Benjamin Drung
[not found] ` <1492538111.18372.1.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-04-19 10:04 ` Leon Romanovsky
[not found] ` <20170419100430.GI14088-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-04-19 15:36 ` Jason Gunthorpe [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=20170419153656.GB29293@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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