[Bug 1745817] Re: autofs 5.1.2-1ubuntu2 crashes on nfs mount
Jonathan
jjcf89 at gmail.com
Fri Apr 13 12:31:25 UTC 2018
Sounds good. Let me know if there is more information I can get out of
gdb.
On Fri, Apr 13, 2018 at 8:14 AM, Andreas Hasenack <andreas at canonical.com>
wrote:
> Thanks for the troubleshooting. I'm taking a look.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1745817
>
> Title:
> autofs 5.1.2-1ubuntu2 crashes on nfs mount
>
> Status in autofs package in Ubuntu:
> Confirmed
>
> Bug description:
> Using the latest autofs package (with libtirpc support) the automount
> process crashes when mounting a nfs share (at least when using IPv4).
>
> I am using a file /etc/auto.master.d/net.autofs to be able to mount
> arbitrary nfs shares to /net:
>
> /net -hosts -intr,soft --timeout=60
>
> When trying to access a share (e.g. with the command "cd
> /net/192.168.1.104" - using the hostname has the same effect)
> automount crashes:
>
> $ sudo systemctl stop autofs.service
> $ source /etc/default/autofs
> $ sudo gdb --args /usr/sbin/automount $OPTIONS -d -v -f
> (gdb) run
> [...]
> attempting to mount entry /net/192.168.1.104
> lookup_mount: lookup(hosts): 192.168.1.104 -> (null)
> get_exports: lookup(hosts): fetchng export list for 192.168.1.104
>
> Thread 6 "automount" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7ffff7fc7700 (LWP 4640)]
> 0x0000000000000000 in ?? ()
> (gdb) bt
> #0 0x0000000000000000 in ?? ()
> #1 0x00007ffff435b8dc in ?? () from /lib/x86_64-linux-gnu/libtirpc.so.1
> #2 0x00007ffff29b11ec in ?? () from /usr/lib/x86_64-linux-gnu/
> autofs/lookup_hosts.so
> #3 0x00007ffff29b23fa in rpc_get_exports () from
> /usr/lib/x86_64-linux-gnu/autofs/lookup_hosts.so
> #4 0x00007ffff29ad516 in ?? () from /usr/lib/x86_64-linux-gnu/
> autofs/lookup_hosts.so
> #5 0x00007ffff29ae013 in lookup_mount () from /usr/lib/x86_64-linux-gnu/
> autofs/lookup_hosts.so
> #6 0x000055555556c70d in do_lookup_mount ()
> #7 0x000055555556d441 in lookup_nss_mount ()
> #8 0x00005555555634d5 in ?? ()
> #9 0x00007ffff7bbd7fc in start_thread () from /lib/x86_64-linux-gnu/
> libpthread.so.0
> #10 0x00007ffff7325b0f in clone () from /lib/x86_64-linux-gnu/libc.so.6
>
> The segfault disappears if the autofs package is recompiled without
> "--with-libtirpc" in debian/rules.
>
> $ lsb_release -rd
> Description: Ubuntu Bionic Beaver (development branch)
> Release: 18.04
>
> $ apt-cache policy autofs
> autofs:
> Installiert: 5.1.2-1ubuntu2
> Installationskandidat: 5.1.2-1ubuntu2
> Versionstabelle:
> *** 5.1.2-1ubuntu2 500
> 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64
> Packages
> 100 /var/lib/dpkg/status
>
> $ apt-cache policy libtirpc1
> libtirpc1:
> Installiert: 0.2.5-1.2
> Installationskandidat: 0.2.5-1.2
> Versionstabelle:
> *** 0.2.5-1.2 500
> 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64
> Packages
> 100 /var/lib/dpkg/status
>
> BTW: libtirpc1 seems to be quite old in Ubuntu, the current release is
> 1.0.2
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/
> 1745817/+subscriptions
>
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1745817
Title:
autofs 5.1.2-1ubuntu2 crashes on nfs mount
Status in autofs package in Ubuntu:
Confirmed
Bug description:
Using the latest autofs package (with libtirpc support) the automount
process crashes when mounting a nfs share (at least when using IPv4).
I am using a file /etc/auto.master.d/net.autofs to be able to mount
arbitrary nfs shares to /net:
/net -hosts -intr,soft --timeout=60
When trying to access a share (e.g. with the command "cd
/net/192.168.1.104" - using the hostname has the same effect)
automount crashes:
$ sudo systemctl stop autofs.service
$ source /etc/default/autofs
$ sudo gdb --args /usr/sbin/automount $OPTIONS -d -v -f
(gdb) run
[...]
attempting to mount entry /net/192.168.1.104
lookup_mount: lookup(hosts): 192.168.1.104 -> (null)
get_exports: lookup(hosts): fetchng export list for 192.168.1.104
Thread 6 "automount" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff7fc7700 (LWP 4640)]
0x0000000000000000 in ?? ()
(gdb) bt
#0 0x0000000000000000 in ?? ()
#1 0x00007ffff435b8dc in ?? () from /lib/x86_64-linux-gnu/libtirpc.so.1
#2 0x00007ffff29b11ec in ?? () from /usr/lib/x86_64-linux-gnu/autofs/lookup_hosts.so
#3 0x00007ffff29b23fa in rpc_get_exports () from /usr/lib/x86_64-linux-gnu/autofs/lookup_hosts.so
#4 0x00007ffff29ad516 in ?? () from /usr/lib/x86_64-linux-gnu/autofs/lookup_hosts.so
#5 0x00007ffff29ae013 in lookup_mount () from /usr/lib/x86_64-linux-gnu/autofs/lookup_hosts.so
#6 0x000055555556c70d in do_lookup_mount ()
#7 0x000055555556d441 in lookup_nss_mount ()
#8 0x00005555555634d5 in ?? ()
#9 0x00007ffff7bbd7fc in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#10 0x00007ffff7325b0f in clone () from /lib/x86_64-linux-gnu/libc.so.6
The segfault disappears if the autofs package is recompiled without
"--with-libtirpc" in debian/rules.
$ lsb_release -rd
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
$ apt-cache policy autofs
autofs:
Installiert: 5.1.2-1ubuntu2
Installationskandidat: 5.1.2-1ubuntu2
Versionstabelle:
*** 5.1.2-1ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
$ apt-cache policy libtirpc1
libtirpc1:
Installiert: 0.2.5-1.2
Installationskandidat: 0.2.5-1.2
Versionstabelle:
*** 0.2.5-1.2 500
500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
BTW: libtirpc1 seems to be quite old in Ubuntu, the current release is
1.0.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1745817/+subscriptions
More information about the foundations-bugs
mailing list