4.8. autofs

The recently released erratum RHBA-2011:1374, that corrected a problem with included map entry removal, introduced a new problem with included map key lookup. The condition that was used with the previous patch was too broad and the map key lookup mechanism failed to find keys in an included multi-mount map entry. The condition has been modified so that keys in multi-mount map entries are now found correctly.

Previously, when a mounted autofs entry was removed from the autofs direct map and the map was reloaded before the map entry expired, the mount failed to unmount. If such a file system was unmounted manually, the next time a process tried to access this file system, the process became unresponsive. With this update, conditions preventing this behavior have been included into the code. The file system can now be accessed normally and the process no longer hangs.

Prior to this update, automount always used the host's IP address instead of the host names. As a result, users had to look up the host name manually when encountering mount problems. This update modifies the name list check so that automount uses now the host name for hosts that have only one IP address.

Previously, autofs submounts incorrectly handled shutdown synchronization and lock restrictions. As a consequence, automount could be unresponsive when submounts expired. With this update, the submount shuts down only after the states ST_SHUTDOWN, ST_SHUTDOWN_PENDING, and ST_SHUTDOWN_FORCE, or when the state changes to ST_READY.

Previously, automount did not correctly parse unmatched brackets in map entry server names. As a consequence, the sanity check for host names in these map entries could fail. Now, unmatched brackets in server names result in a syntax error being reported and the check no longer fails.

Previously, the automount logged confusing error messages when syntax errors occurred in map entry locations. This update modifies these messages and displays more informative messages were possible.

Previously, LDAP servers did not correctly return an opaque cookie to check for additional results when getting paged results from the server on 64-bit PowerPC and IBM System z platforms due to slightly different criteria for deciding if there are more results. As a consequence, the autofs internal functions did not detect when paged result sets were not supported. This update modifies the underlying source code so that autofs now correctly detects whether the paged results are updated.

Previously, an incorrect check for the presence of additional addresses for a host led to the IP address being used for mounting instead of the host name. As a consequence the IP address was displayed instead of the host name when listing system mounts, even when the host had only a single address. This update modifies the check so that the IP address is used only if a host has multiple IP addresses.

Previously, incorrect identification of the map entry source caused a failure during the key lookup. As a consequence, map lookups for an automount, where a a key was present in a file map and the same key was also found in an included map, failed if the file map entry was removed and a lookup was performed before a re-load is issued. This update modifies the key lookup code and the lookup works now as expected.

Previously, automount could become unresponsive when reloading a master map that included a combination of direct and indirect maps due to incorrect lock ordering. This update corrects the logic used to determine if the lookup needs to continue into included maps.

Previously, map entries were always mounted using proximity and response time instead of bind mounting when adding a random selection of a host if the mount was local. This update modifies this behavior and also adds the "nobind" option to allow the previous behavior to be forced if needed.

Previously, the map key lookup mechanism did not find keys in an included multi-mount map entry. This update modifies the lookup mechanism so that keys in multi-mount map entries are now found correctly.

Previously, the stack allocation function of the temporary work space was used within a loop in the function lookup_ghost(). As a consequence, a stack overflow could occur and automount then failed with a segmentation fault. This update corrects the allocation usage and the stack overflows no longer occurs.

With this update,the "--dumpmaps" option to dump maps has been added to dump in autofs.