[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#849487: marked as done (/sbin/umount.nfs4: error while loading shared libraries:)

Your message dated Tue, 15 Mar 2022 02:26:47 +0100
with message-id <ae5cb33016da8c03b4b0c5cfe6cdf398fe8f6c1f.camel@decadent.org.uk>
and subject line Re: /sbin/umount.nfs4: error while loading shared libraries:
has caused the Debian Bug report #849487,
regarding /sbin/umount.nfs4: error while loading shared libraries:
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
849487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849487
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: nfs-common
Version: 1:1.3.4-2
Severity: important

Either mounting or unmounting nfs shares I get:
/sbin/umount.nfs4: error while loading shared libraries: R_PPC_REL24
relocation at 0x205cc8ec for symbol 'time' out of range

Please note that I recognize this only on ppc32 platform which
indeed indicates that -fPIC wasn't use on buildtime?

reverting to 1:1.3.4-2 works fine


-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100007    2   udp    962  ypbind
    100007    1   udp    962  ypbind
    100007    2   tcp    963  ypbind
    100007    1   tcp    963  ypbind
-- /etc/default/nfs-common --
NEED_STATD=
STATDOPTS=
NEED_IDMAPD=
NEED_GSSD=
-- /etc/idmapd.conf --
[General]
Verbosity = 0
Pipefs-Directory = /run/rpc_pipefs
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
-- /etc/fstab --
# The nfs shares
[...]

baumbart:/home/archiv/DOWNLOAD /home/archiv/DOWNLOAD nfs4 rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.200.203,local_lock=none,addr=192.168.200.1 0 0

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (100, 'experimental')
Architecture: powerpc (ppc)

Kernel: Linux 4.9.0-aragorn-lxtec-ppc
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nfs-common depends on:
ii  adduser              3.115
ii  init-system-helpers  1.46
ii  keyutils             1.5.9-9
ii  libc6                2.24-8
ii  libcap2              1:2.25-1
ii  libcomerr2           1.43.3-1
ii  libdevmapper1.02.1   2:1.02.137-1
ii  libevent-2.0-5       2.0.21-stable-2.1
ii  libgssapi-krb5-2     1.15-1
ii  libk5crypto3         1.15-1
ii  libkeyutils1         1.5.9-9
ii  libkrb5-3            1.15-1
ii  libmount1            2.28.2-1
ii  libnfsidmap2         0.25-5.1
ii  libtirpc1            0.2.5-1.1
ii  libwrap0             7.6.q-26
ii  lsb-base             9.20161125
ii  rpcbind              0.2.3-0.5
ii  ucf                  3.0036

Versions of packages nfs-common recommends:
ii  python  2.7.13-1

Versions of packages nfs-common suggests:
pn  open-iscsi  <none>
pn  watchdog    <none>

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 1:1.3.4-2.1

On Tue, 27 Dec 2016 20:38:20 +0100 Elimar Riesebieter
<riesebie@lxtec.de> wrote:
> Package: nfs-common
> Version: 1:1.3.4-2
> Severity: important
> 
> Either mounting or unmounting nfs shares I get:
> /sbin/umount.nfs4: error while loading shared libraries: R_PPC_REL24
> relocation at 0x205cc8ec for symbol 'time' out of range
> 
> Please note that I recognize this only on ppc32 platform which
> indeed indicates that -fPIC wasn't use on buildtime?

It is not correct to build executables as PIC, but we do build them
with PIE by default now.

> reverting to 1:1.3.4-2 works fine
[...]

I suppose this should say "1:1.3.4-1", as you reported this against -2
and that was the latest version available at that time.

I looked at the binaries in different versions of nfs-common from 2016-
2017, and the toolchain changes made around the same time.  It appears
that dpkg forced PIE on for powerpc before this was properly working in
gcc, but later stopped doing this.  Later still, gcc implemented PIE
properly on powerpc.  Only this version of nfs-common seems to have
been built with the broken combination.

Therefore, I am marking this fixed in the following version.

Ben.

-- 
Ben Hutchings
Never put off till tomorrow what you can avoid all together.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: