Comment 34 for bug 214041

In this particular case its because i told it to do something bogus with the
mount options. The SELinux denial from the above line is expected and was
encountered when I was working on doing so SELinux/NFS testing for other
purposes. Historically mount.nfs would kick it back at me instantly but not any
more. This is not by any means common, a much more reasonable failure scenario
(and one that happened under binary mount options) would be:

mount server:/export /import -o context=system_u:object_r:httpd_t:s0

This is invalid but not nearly as strange and contrived as my previous mount
command and the user should get EACCES, but instead, after 2 minutes they get:

mount.nfs: Connection timed out

which does tell the real problem. Even if we let it retry on EACCES for 2
minutes it needs to fail with EACCES. If it pretends it was a timeout problem
it will send the user looking at non permission related problems...