Bug 173194 - race condition when expiring ghosted autofs mounts
Summary: race condition when expiring ghosted autofs mounts
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Jeff Moyer
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks: 168429
TreeView+ depends on / blocked
 
Reported: 2005-11-14 21:11 UTC by Jeff Moyer
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version: RHSA-2006-0132
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-03-07 20:47:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:808 0 normal SHIPPED_LIVE Important: kernel security update 2005-10-27 04:00:00 UTC
Red Hat Product Errata RHSA-2006:0132 0 qe-ready SHIPPED_LIVE Moderate: Updated kernel packages available for Red Hat Enterprise Linux 4 Update 3 2006-03-09 16:31:00 UTC

Description Jeff Moyer 2005-11-14 21:11:51 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050719 Red Hat/1.0.6-1.4.1 Firefox/1.0.6

Description of problem:
For browsable autofs maps, a mount request that arrives at the same time 
an expire is happening can fail to perform the needed mount.

This happens becuase the directory exists and so the revalidate succeeds 
when we need it to fail so that lookup is called on the same dentry to do 
the mount. Instead lookup is called on the next path component which 
should be whithin the mount, but the parent isn't mounted. 

The solution is to allow the revalidate to continue and perform the mount 
as no directory creation (at mount time) is needed for browsable mount 
entries.


Version-Release number of selected component (if applicable):


How reproducible:
Sometimes

Steps to Reproduce:
I put together the following reproducer for this:

auto.master:
/multi	/etc/auto.multi --timeout=4 --ghost

and auto.multi contains
dir     /       segfault:/export/multi \
        /foo    segfault:/export/multi/thefoodir

Then, I simply run the following script:

#!/bin/bash
while true;
do
	cat /segfault/multi/foo/bar > /dev/null
	if [ $? -ne 0 ]; then
		echo "Failed!"
		exit 1
	fi
	sleep 4
done

Once we get a mount request at the same time as a pending expiry, we will
trigger this bug.  In my testing, this typically occurs withing the first 3
iterations of the loop.

Additional info:

Comment 2 Linda Wang 2005-11-23 17:17:01 UTC
committed in -22.25

Comment 6 Red Hat Bugzilla 2006-03-07 20:47:28 UTC
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 the 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-2006-0132.html



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