Hide Forgot
When checking a directory tree, the kernel module could, in some circumstances, incorrectly decide the tree was not busy. An active offset mount with an open file handle being used for expires caused the file handle to not count toward the busyness check. This resulted in mount requests being made for already mounted offsets. With this update, the kernel module check has been corrected and incorrect mount requests are no longer generated.
This fix is part of the autofs4 bug fix update for RHEL-5.3 and so needs to be applied to RHEL-4 also. Ian
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Committed in 78.29.EL . RPMS are available at http://people.redhat.com/vgoyal/rhel4/
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: When checking a directory tree the kernel module can incorrectly decide that the tree isn't busy. This happens for the case of an active offset mount as we follow past the active offset mount, which has an open file handle which is used for expires, causing the file handle not to count toward the busyness check. This results in a mount request for an already mounted offset. The check in the kernel module has now been corrected and incorrect mount requests are not generated.
Release note updated. 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. Diffed Contents: @@ -1 +1 @@ -When checking a directory tree the kernel module can incorrectly decide that the tree isn't busy. This happens for the case of an active offset mount as we follow past the active offset mount, which has an open file handle which is used for expires, causing the file handle not to count toward the busyness check. This results in a mount request for an already mounted offset. The check in the kernel module has now been corrected and incorrect mount requests are not generated.+When checking a directory tree the kernel module can incorrectly decide that the tree isn't busy. This happens for the case of an active offset mount as we follow past the active offset mount, which has an open file handle that is used for expires, causing the file handle not to count toward the busyness check. This results in a mount request for an already mounted offset. The check in the kernel module has now been corrected and incorrect mount requests are not generated.
Release note updated. 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. Diffed Contents: @@ -1 +1 @@ -When checking a directory tree the kernel module can incorrectly decide that the tree isn't busy. This happens for the case of an active offset mount as we follow past the active offset mount, which has an open file handle that is used for expires, causing the file handle not to count toward the busyness check. This results in a mount request for an already mounted offset. The check in the kernel module has now been corrected and incorrect mount requests are not generated.+When checking a directory tree, the kernel module could, in some circumstances, incorrectly decide the tree was not busy. An active offset mount with an open file handle being used for expires caused the file handle to not count toward the busyness check. This resulted in mount requests being made for already mounted offsets. With this update, the kernel module check has been corrected and incorrect mount requests are no longer generated.
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/RHSA-2009-1024.html