8.5. autofs

Bug Fixes

BZ#859078

Under certain circumstances, the autofs utility did not respect all configured settings and used the UDP protocol to probe availability of network file systems. This can lead to some servers refusing the connection with the message:

Client x.x.x.x is violating the NFSv4 specification by sending a UDP/IP datagram to the NFSv4 server.

With this update, autofs has been modified to respect explicitly defined NFSv4 requests, thus fixing this bug.

BZ#886623

Due to changes made to the autofs utility, when probing server availability at mount time, mounts using the RDMA protocol are no longer recognized. With this update, autofs has been modified not to probe availability for mounts that use the RDMA protocol.

BZ#903944

Previously, the autofs utility ignored the --random-multimount-selection option. Consequently, this setting was not used when mounting local file systems even when it was given. This bug has been fixed and --random-multimount-selection now works as expected.

BZ#908020

Previously, when two nearly simultaneous mount requests appeared, NFS mounts mounted by the autofs utility sometimes terminated. This was caused by using invalid protoent structures to identify the protocol. With this update, autofs has been modified to use numeric protocol IDs, instead of protoent structures. As a result, attempts to mount NFS no longer fail in the described scenario.

BZ#971131

Prior to this update, the autofs master map parser did not recognize the SELinux context= option and returned a syntax error when the option was used. The master map parser has been updated to recognize SELinux context= that can now be used without complications.

BZ#974884

Previously, the autofs utility did not recognize the allowed limit of maximum opened files after it was increased by the system administrator. Consequently, the default limit was used regardless of the new configuration. With this update, autofs has been modified to check for changes of this limit and to apply them correctly.

BZ#996749

Previously, the libldap library was not initialized in a thread-safe manner. Consequently, when running automount, the ber_memalloc_x() function could have terminated unexpectedly with a segmentation fault. With this update, the initializaliton of libldap has been modified to be thread-safe and ber_memalloc_x() no longer crashes in the aforementioned scenario. (BZ#996749)

BZ#979929

When the automount daemon was checking host availability and one of the network interfaces was marked "DOWN", automount terminated with a segmentation fault. With this update, a check for this case has been added and the segmentation fault no longer occurs.

BZ#994296

When the automount daemon received a shutdown signal, executing the autofs reload command caused automount to stop running when multiple maps were being removed from the auto.master map. A patch has been added to fix this bug and automount no longer terminates in the described case.

BZ#994297

A change that removed a code for adding the current map entry caused wildcard indirect multi-mount map entries to fail to mount. A patch to fix wildcard multi-map regression has been added and map entries now mount successfully.

BZ#1002896

Due to an execution order race that occurred when creating an expire thread, the automount daemon became unresponsive. The code that handled the expire thread creation has been modified to prevent the aforementioned problem.

BZ#996749

Previously, no locking was performed around LDAP initialization calls. However, these functions are not thread-safe and race conditions could have occurred. With this update, the locking has been added and the risk of race condition is now reduced.

Enhancements

BZ#982103

The description of the TIMEOUT configuration option has been enhanced in the autofs man page. The description now explains the internal default configuration more clearly.

BZ#852327

The autofs utility has been updated to provide the ability to dump its mount maps in a simple <key, value> format in addition to the existing informational format.