This bugzilla has Keywords: Regression.  

Since no regressions are allowed between releases, 
it is also being proposed as a blocker for this release.  

Please resolve ASAP.

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.

*** This bug has been marked as a duplicate of 212249 ***

This bug is for to re-instate the negative timeout
within the autofs4 kernel module. Bug #212249 is
actually is tracking the addition of this functionality
in the user space daemon.

A separate task.

Ian

The addition of mount failure caching proved to be much more
complex than I had hoped and there was a reported oops that
I wasn't able to track down.

This functionality has been implemented in the user space
daemon for the time being but we would prefer it be handled
in the kernel module as it should use less overhead.

So I need to defer this.
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.

Updating PM score.

As described in comment #5 it isn't viable or sensible to get the
caching of failed mount requests to work within the autofs4 kernel
module (this stopped working due to VFS changes in the 2.6 kernel).

Since considerable effort has been invested in providing this
functionality in the user space autofs application in our 2.6 kernel
based products I'm closing this bug as WONTTFIX.

Ian