Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1166457 - Autofs unable to mount indirect after attempt to mount wildcard
Autofs unable to mount indirect after attempt to mount wildcard
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: autofs (Show other bugs)
7.1
Unspecified Unspecified
urgent Severity urgent
: rc
: ---
Assigned To: Ian Kent
Yongcheng Yang
Jaromir Hradilek
:
Depends On: 1163957
Blocks: 1205790 1133060
  Show dependency treegraph
 
Reported: 2014-11-20 21:16 EST by Ian Kent
Modified: 2015-11-19 08:00 EST (History)
5 users (show)

See Also:
Fixed In Version: autofs-5.0.7-49
Doc Type: Bug Fix
Doc Text:
Cause: when an "ls *" is done of the root of an indirect mount, autofs will attempt to literally mount the key '*' causing it to be added to the negative cache. Consequence: if this is done before a valid mount, autofs fails on further mount attempts inside the mountpoint, valid or not. Fix: fixed by checking for and not adding the wildcard key when updating the negative cache. Result: the wildcard map entry continues to function following a 'ls *' within the root of an autofs mountpoint.
Story Points: ---
Clone Of: 1163957
Environment:
Last Closed: 2015-11-19 08:00:45 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Patch - make negative cache update consistent for all lookup modules (2.95 KB, patch)
2015-05-24 21:29 EDT, Ian Kent
no flags Details | Diff
Patch - ensure negative cache isn't updated on remount (1.49 KB, patch)
2015-05-24 21:30 EDT, Ian Kent
no flags Details | Diff
Patch - dont add wildcard to negative cache (1.35 KB, patch)
2015-05-24 21:31 EDT, Ian Kent
no flags Details | Diff


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2417 normal SHIPPED_LIVE Moderate: autofs security, bug fix and enhancement update 2015-11-19 06:23:21 EST

  None (edit)
Comment 1 Ian Kent 2015-05-24 21:29:37 EDT
Created attachment 1029319 [details]
Patch - make negative cache update consistent for all lookup modules
Comment 2 Ian Kent 2015-05-24 21:30:31 EDT
Created attachment 1029320 [details]
Patch - ensure negative cache isn't updated on remount
Comment 3 Ian Kent 2015-05-24 21:31:28 EDT
Created attachment 1029321 [details]
Patch - dont add wildcard to negative cache
Comment 5 XuWang 2015-08-27 04:41:25 EDT
run /CoreOS/autofs/Regression/bz1163957-unable-mount-indirect-after-ls-with-wildcard for autofs-5.0.7-53.el7, seems good.

the previous version output:
:: [   FAIL   ] :: Command 'ls -ld /automount/dir{1,2}' (Expected 0, got 2)

the autofs-5.0.7-53.el7 output:

[03:26:56 root@ ~~]# ls -ld /automount/*
ls: cannot access /automount/*: No such file or directory
:: [   PASS   ] :: Running 'ls -ld /automount/*' (Expected 2, got 2)
--------------------------------------------------------------------------------
[03:26:56 root@ ~~]# ls -ld /automount/dir{1,2}
drwxr-xr-x. 2 root root 6 Aug 27 03:26 /automount/dir1
drwxr-xr-x. 2 root root 6 Aug 27 03:26 /automount/dir2
:: [   PASS   ] :: Running 'ls -ld /automount/dir{1,2}' (Expected 0, got 0)

also run stress, bugzillas, regressions, connectathon for autofs-5.0.7-53.el7, covered ppc64, x86_64, s390x, ppc64le no new issues.

I think I can set the status of this bug to be verified.
Comment 8 errata-xmlrpc 2015-11-19 08:00:45 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-2417.html

Note You need to log in before you can comment on or make changes to this bug.