Description of problem: There is a slight window where we could have one map in a multimap entry read a second after the previous map, thus invalidating all of the cache entries created by the previous map. This results in incorrect results in some configurations, such as duplicate keys, or a wildcard key in the first map but not in subsequent maps. This has been tripped over by at least one customer. I will attempt to create an RHTS test for this, though I think it will be difficult to trigger.
Created attachment 321937 [details] Pass time into the lookup_ghost functions This patch should address the problem of incorrectly clearing the cache from one module in a multi-map configuration.
A fix for this is available in autofs versions 4.1.3-235.4 and later.
Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: * the multi-map lookup code contained a race that could result in automount reading two maps in quick succession. Reading the second map invalidated the cache entries created by the first map, and in some configurations, this led to problematic or nonsensical results such as duplicate keys, or a wildcard key in the first map not present in subsequent maps. This would result in failed lookups for valid automount keys. The lookup code now passes time into the lookup_ghost functions, and therefore avoids incorrectly clearing the cache. Automount now reliably looks up valid keys.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0991.html