[Bug 1503034] Re: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup

[Mathew Hodson]

** Description changed:

  I'm running Wily Beta 2, updated to the latest packages in the wily
  repository, with autofs-ldap using mounts stored in LDAP. On startup
  systemd immediately puts autofs into a failed state as it segfaults when
  reading the auto.master.
  
  Autofs & autofs-ldap version is 5.1.1-1ubuntu2.
+ 
+ [Impact]
+ 
+ This bug prevents the autofs-ldap module from loading, and causes it to
+ segfault on startup. The proposed fix allows the module to load
+ normally. The fix initialises configuration cache before it is first
+ used (it is the access to the uninitialised cache which causes the
+ segfault).
+ 
+ [Test Case]
+ 
+ Install the autofs-ldap package and have it read an automount map from
+ LDAP. The necessary auto.master & ldap.conf configuration is dependent
+ on the LDAP server that provides the automount maps.
+ 
+ [Regression Potential]
+ 
+ Given the shipped package does not load at all, it can't be a regression
+ on the shipped binary.
+ 
+ [Other Info]
  
  The log in journalctl looks like this:
  
  Oct 05 15:47:45 <hostname> autofs[2232]: * Starting automount...
  Oct 05 15:47:45 <hostname> automount[2240]: Starting automounter version 5.1.1, master map /etc/auto.master
  Oct 05 15:47:45 <hostname> automount[2240]: using kernel protocol version 5.02
  Oct 05 15:47:45 <hostname> automount[2240]: lookup_nss_read_master: reading master file /etc/auto.master
  Oct 05 15:47:45 <hostname> automount[2240]: parse_init: parse(sun): init gathered global options: (null)
  Oct 05 15:47:45 <hostname> automount[2240]: spawn_mount: mtab link detected, passing -n to mount
  Oct 05 15:47:45 <hostname> automount[2240]: spawn_umount: mtab link detected, passing -n to mount
  Oct 05 15:47:45 <hostname> automount[2240]: lookup_read_master: lookup(file): read entry /net
  Oct 05 15:47:45 <hostname> automount[2240]: lookup_read_master: lookup(file): read entry +dir:/etc/auto.master.d
  Oct 05 15:47:45 <hostname> automount[2240]: lookup_nss_read_master: reading master dir /etc/auto.master.d
  Oct 05 15:47:45 <hostname> automount[2240]: lookup(dir): dir map /etc/auto.master.d missing or not readable
  Oct 05 15:47:45 <hostname> automount[2240]: lookup(file): failed to read included master map dir:/etc/auto.master.d
  Oct 05 15:47:45 <hostname> automount[2240]: lookup_read_master: lookup(file): read entry +auto.master
  Oct 05 15:47:45 <hostname> automount[2240]: lookup_nss_read_master: reading master files auto.master
  Oct 05 15:47:45 <hostname> automount[2240]: parse_init: parse(sun): init gathered global options: (null)
  Oct 05 15:47:45 <hostname> automount[2240]: lookup_nss_read_master: reading master ldap auto.master
  Oct 05 15:47:45 <hostname> kernel: automount[2240]: segfault at 0 ip 00007fb87ade5bcb sp 00007ffc30b34550 error 4 in lookup_ldap.so[7fb87adca000+38000]
  Oct 05 15:47:47 <hostname> autofs[2232]: ...fail!
  Oct 05 15:47:47 <hostname> systemd[1]: autofs.service: Control process exited, code=exited status=1
  
  This occurs whenever the service is started with the line in auto.master
  which loads the ldap mounts. The line which causes the issue is
  "+ldap:automountMapName=auto.master.linux,ou=automount,ou=<location>,ou=<group>,o=<group>,dc=<base>,dc=com",
  and this configuration worked on 14.04, 14.10 and 15.04.
- 
- [Impact] This bug prevents the autofs-ldap module from loading, and
- causes it to segfault on startup. The proposed fix allows the module to
- load normally. The fix initialises configuration cache before it is
- first used (it is the access to the uninitialised cache which causes the
- segfault).
- 
- [Test Case] Install the autofs-ldap package and have it read an
- automount map from LDAP. The necessary auto.master & ldap.conf
- configuration is dependent on the LDAP server that provides the
- automount maps.
- 
- [Regression Potential] Given the shipped package does not load at all,
- it can't be a regression on the shipped binary.

** Changed in: autofs (Ubuntu Wily)
       Status: Confirmed => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1503034

Title:
  Autofs 5.1.1-1ubuntu2 crashes with segfault on startup

Status in autofs package in Ubuntu:
  Fix Released
Status in autofs source package in Wily:
  Triaged

Bug description:
  I'm running Wily Beta 2, updated to the latest packages in the wily
  repository, with autofs-ldap using mounts stored in LDAP. On startup
  systemd immediately puts autofs into a failed state as it segfaults
  when reading the auto.master.

  Autofs & autofs-ldap version is 5.1.1-1ubuntu2.

  [Impact]

  This bug prevents the autofs-ldap module from loading, and causes it
  to segfault on startup. The proposed fix allows the module to load
  normally. The fix initialises configuration cache before it is first
  used (it is the access to the uninitialised cache which causes the
  segfault).

  [Test Case]

  Install the autofs-ldap package and have it read an automount map from
  LDAP. The necessary auto.master & ldap.conf configuration is dependent
  on the LDAP server that provides the automount maps.

  [Regression Potential]

  Given the shipped package does not load at all, it can't be a
  regression on the shipped binary.

  [Other Info]

  The log in journalctl looks like this:

  Oct 05 15:47:45 <hostname> autofs[2232]: * Starting automount...
  Oct 05 15:47:45 <hostname> automount[2240]: Starting automounter version 5.1.1, master map /etc/auto.master
  Oct 05 15:47:45 <hostname> automount[2240]: using kernel protocol version 5.02
  Oct 05 15:47:45 <hostname> automount[2240]: lookup_nss_read_master: reading master file /etc/auto.master
  Oct 05 15:47:45 <hostname> automount[2240]: parse_init: parse(sun): init gathered global options: (null)
  Oct 05 15:47:45 <hostname> automount[2240]: spawn_mount: mtab link detected, passing -n to mount
  Oct 05 15:47:45 <hostname> automount[2240]: spawn_umount: mtab link detected, passing -n to mount
  Oct 05 15:47:45 <hostname> automount[2240]: lookup_read_master: lookup(file): read entry /net
  Oct 05 15:47:45 <hostname> automount[2240]: lookup_read_master: lookup(file): read entry +dir:/etc/auto.master.d
  Oct 05 15:47:45 <hostname> automount[2240]: lookup_nss_read_master: reading master dir /etc/auto.master.d
  Oct 05 15:47:45 <hostname> automount[2240]: lookup(dir): dir map /etc/auto.master.d missing or not readable
  Oct 05 15:47:45 <hostname> automount[2240]: lookup(file): failed to read included master map dir:/etc/auto.master.d
  Oct 05 15:47:45 <hostname> automount[2240]: lookup_read_master: lookup(file): read entry +auto.master
  Oct 05 15:47:45 <hostname> automount[2240]: lookup_nss_read_master: reading master files auto.master
  Oct 05 15:47:45 <hostname> automount[2240]: parse_init: parse(sun): init gathered global options: (null)
  Oct 05 15:47:45 <hostname> automount[2240]: lookup_nss_read_master: reading master ldap auto.master
  Oct 05 15:47:45 <hostname> kernel: automount[2240]: segfault at 0 ip 00007fb87ade5bcb sp 00007ffc30b34550 error 4 in lookup_ldap.so[7fb87adca000+38000]
  Oct 05 15:47:47 <hostname> autofs[2232]: ...fail!
  Oct 05 15:47:47 <hostname> systemd[1]: autofs.service: Control process exited, code=exited status=1

  This occurs whenever the service is started with the line in
  auto.master which loads the ldap mounts. The line which causes the
  issue is
  "+ldap:automountMapName=auto.master.linux,ou=automount,ou=<location>,ou=<group>,o=<group>,dc=<base>,dc=com",
  and this configuration worked on 14.04, 14.10 and 15.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1503034/+subscriptions