From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Honggang Li <honli@redhat.com>, Itay Aveksis <itayav@nvidia.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Alaa Hleihel <alaa@nvidia.com>,
Doug Ledford <dledford@redhat.com>
Subject: Re: rdma-core spec weird behavior on Fedora
Date: Mon, 8 Feb 2021 15:10:53 +0200 [thread overview]
Message-ID: <20210208131053.GC20265@unreal> (raw)
In-Reply-To: <20210208125900.GX4247@nvidia.com>
On Mon, Feb 08, 2021 at 08:59:00AM -0400, Jason Gunthorpe wrote:
> On Sun, Feb 07, 2021 at 10:06:49AM +0200, Leon Romanovsky wrote:
> > Hi Honggang,
> >
> > Your commit b02de521022a ("redhat: Remove base package dependency from all sub-packages")
> > removes protection from rdma-core when user performs "dnf autoremove".
> >
> > Before your patch, systemd was dependent on libibverbs and latter
> > required rdma-core. After your patch, the last link is lost and
> > rdma-core marked as orphaned package.
> >
> > Any attempt to install rdma-core as standalone package will have the
> > following errors, due to the library dependency of udevadm.
> > [leonro@c rdma-core]$ ldd /sbin/udevadm | grep verbs
> > libibverbs.so.1 => not found
>
> well that makes no sense, since when is udevadm connected to
> libibverbs?
>
> $ ldd `which udevadm`
> linux-vdso.so.1 (0x00007ffcc09ef000)
> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f394bec3000)
> libkmod.so.2 => /lib/x86_64-linux-gnu/libkmod.so.2 (0x00007f394bea8000)
> libacl.so.1 => /lib/x86_64-linux-gnu/libacl.so.1 (0x00007f394be9d000)
> libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 (0x00007f394be46000)
> libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007f394be1b000)
> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f394bdf8000)
> /lib64/ld-linux-x86-64.so.2 (0x00007f394c1b6000)
> liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f394bdcd000)
> libcrypto.so.1.1 => /lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x00007f394baf7000)
> libpcre2-8.so.0 => /lib/x86_64-linux-gnu/libpcre2-8.so.0 (0x00007f394ba67000)
> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f394ba61000)
This is from my laptop and it is connected:
➜ kernel git:(m/msix-v6) ldd /sbin/udevadm
linux-vdso.so.1 (0x00007fffc4bf2000)
libsystemd-shared-246.so => /usr/lib/systemd/libsystemd-shared-246.so (0x00007f70f69ef000)
libkmod.so.2 => /lib64/libkmod.so.2 (0x00007f70f69c0000)
libacl.so.1 => /lib64/libacl.so.1 (0x00007f70f69b6000)
libblkid.so.1 => /lib64/libblkid.so.1 (0x00007f70f6981000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f70f6966000)
libc.so.6 => /lib64/libc.so.6 (0x00007f70f679b000)
libcap.so.2 => /lib64/libcap.so.2 (0x00007f70f6792000)
libcrypt.so.2 => /lib64/libcrypt.so.2 (0x00007f70f6758000)
libcryptsetup.so.12 => /lib64/libcryptsetup.so.12 (0x00007f70f66e3000)
libgcrypt.so.20 => /lib64/libgcrypt.so.20 (0x00007f70f65be000)
libidn2.so.0 => /lib64/libidn2.so.0 (0x00007f70f659d000)
libip4tc.so.2 => /lib64/libip4tc.so.2 (0x00007f70f6593000)
liblz4.so.1 => /lib64/liblz4.so.1 (0x00007f70f6573000)
libmount.so.1 => /lib64/libmount.so.1 (0x00007f70f6530000)
libcrypto.so.1.1 => /lib64/libcrypto.so.1.1 (0x00007f70f6243000)
libp11-kit.so.0 => /lib64/libp11-kit.so.0 (0x00007f70f6111000)
libpam.so.0 => /lib64/libpam.so.0 (0x00007f70f60ff000)
librt.so.1 => /lib64/librt.so.1 (0x00007f70f60f4000)
libseccomp.so.2 => /lib64/libseccomp.so.2 (0x00007f70f60d0000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f70f60a3000)
libzstd.so.1 => /lib64/libzstd.so.1 (0x00007f70f5fce000)
liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f70f5fa2000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f70f5f9b000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f70f5f79000)
/lib64/ld-linux-x86-64.so.2 (0x00007f70f6d29000)
libz.so.1 => /lib64/libz.so.1 (0x00007f70f5f5d000)
libattr.so.1 => /lib64/libattr.so.1 (0x00007f70f5f55000)
libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f70f5f4c000)
libdevmapper.so.1.02 => /lib64/libdevmapper.so.1.02 (0x00007f70f5eef000)
libssl.so.1.1 => /lib64/libssl.so.1.1 (0x00007f70f5e53000)
libargon2.so.1 => /lib64/libargon2.so.1 (0x00007f70f5e4a000)
libjson-c.so.5 => /lib64/libjson-c.so.5 (0x00007f70f5e35000)
libgpg-error.so.0 => /lib64/libgpg-error.so.0 (0x00007f70f5e10000)
libunistring.so.2 => /lib64/libunistring.so.2 (0x00007f70f5c8d000)
libpcap.so.1 => /lib64/libpcap.so.1 (0x00007f70f5c3e000)
libffi.so.6 => /lib64/libffi.so.6 (0x00007f70f5c33000)
libaudit.so.1 => /lib64/libaudit.so.1 (0x00007f70f5c04000)
libeconf.so.0 => /lib64/libeconf.so.0 (0x00007f70f5bfa000)
libm.so.6 => /lib64/libm.so.6 (0x00007f70f5ab4000)
libpcre2-8.so.0 => /lib64/libpcre2-8.so.0 (0x00007f70f5a1d000)
libudev.so.1 => /lib64/libudev.so.1 (0x00007f70f59f2000)
libibverbs.so.1 => /lib64/libibverbs.so.1 (0x00007f70f59cf000)
libcap-ng.so.0 => /lib64/libcap-ng.so.0 (0x00007f70f59c7000)
libnl-route-3.so.200 => /lib64/libnl-route-3.so.200 (0x00007f70f5944000)
libnl-3.so.200 => /lib64/libnl-3.so.200 (0x00007f70f5921000)
➜ kernel git:(m/msix-v6) cat /etc/os-release
NAME=Fedora
VERSION="33 (Workstation Edition)"
ID=fedora
VERSION_ID=33
VERSION_CODENAME=""
PLATFORM_ID="platform:f33"
PRETTY_NAME="Fedora 33 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:33"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f33/system-administrators-guide/"
SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=33
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=33
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
VARIANT="Workstation Edition"
VARIANT_ID=workstation
>
> Jason
next prev parent reply other threads:[~2021-02-08 13:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 8:06 rdma-core spec weird behavior on Fedora Leon Romanovsky
2021-02-08 12:59 ` Jason Gunthorpe
2021-02-08 13:10 ` Leon Romanovsky [this message]
2021-02-08 13:15 ` Alaa Hleihel
2021-02-08 13:26 ` Leon Romanovsky
2021-02-08 13:21 ` Jason Gunthorpe
2021-02-08 13:31 ` Leon Romanovsky
2021-02-08 14:08 ` Jason Gunthorpe
2021-02-08 14:31 ` Leon Romanovsky
2021-02-08 15:35 ` Jason Gunthorpe
2021-02-08 15:59 ` Leon Romanovsky
2021-02-08 18:18 ` Jason Gunthorpe
2021-02-10 11:54 ` Leon Romanovsky
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=20210208131053.GC20265@unreal \
--to=leon@kernel.org \
--cc=alaa@nvidia.com \
--cc=dledford@redhat.com \
--cc=honli@redhat.com \
--cc=itayav@nvidia.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.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 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.