From: Ian Kent <raven@themaw.net>
To: Leonardo Chiquitto <leonardo.lists@gmail.com>
Cc: autofs@linux.kernel.org, David Howells <dhowells@redhat.com>
Subject: Re: stat -L triggering mount (behavior change starting with 2.6.38-rc1)
Date: Fri, 01 Apr 2011 12:27:18 +0800 [thread overview]
Message-ID: <1301632038.2880.11.camel@perseus> (raw)
In-Reply-To: <AANLkTi=FfdPyVB5oiSFPbgms9Nej8LW8yfGMiYmufSCu@mail.gmail.com>
On Mon, 2011-03-28 at 19:53 -0300, Leonardo Chiquitto wrote:
> Hello,
>
> After the update to 2.6.38, I noticed that AutoFS started to mount volumes
> at times it normally wouldn't. More specifically, "ls -la" inside an AutoFS
> mount point will trigger the mount of all available maps.
>
> This can be reproduced with a simple indirect mount setup:
>
> # cat /etc/auto.master
> /data /etc/auto.data
>
> # cat /etc/auto.data
> isos -fstype=nfs4,ro,rsize=8192,wsize=8192,intr,nolock,nosuid libre:/isos
>
> # egrep '(autofs|nfs4)' /proc/mounts
> /etc/auto.data /data autofs rw,relatime,fd=7,pgrp=4300,timeout=600,minproto=5,\
> maxproto=5,indirect 0 0
>
> # stat -L /data/isos > /dev/null
How about an strace of this please?
>
> # egrep '(autofs|nfs4)' /proc/mounts
> /etc/auto.data /data autofs rw,relatime,fd=7,pgrp=4300,timeout=600,minproto=5,\
> maxproto=5,indirect 0 0
> libre:/isos /data/isos nfs4 ro,nosuid,relatime,vers=4,(.. more mount
> options ..) 0 0
>
> Bisecting the changes between 2.6.37 and 2.6.38, I found that 2.6.38-rc1
> exhibits the new behavior already. I went as near 2.6.37 as I could and verified
> that commit b650c858c2 (autofs4: Merge the remaining dentry ops tables) also
> shows the new behavior. I tried to bisect the remaining ~18 commits
> but everything
> I tested/built ended up unbootable.
>
> I also tested mainline and verified that the problem is still there.
There where two significant patch series merged in 2.6.38 which were to
similar parts of the VFS. One was the vfs-scale series and the other was
the vfs-automount series. So 2.6.38 had significant autofs changes.
I think the mount storm your seeing would be due to this check not
catching lstat(2) calls, but AFAICS it should catch this case:
if (!(flags & LOOKUP_FOLLOW) &&
!(flags & (LOOKUP_CONTINUE | LOOKUP_DIRECTORY |
LOOKUP_OPEN | LOOKUP_CREATE)))
return -EISDIR;
What do you think David?
Ian
next prev parent reply other threads:[~2011-04-01 4:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 22:53 stat -L triggering mount (behavior change starting with 2.6.38-rc1) Leonardo Chiquitto
2011-04-01 4:27 ` Ian Kent [this message]
2011-04-01 4:55 ` Ian Kent
2011-04-01 9:19 ` David Howells
2011-04-01 12:20 ` Leonardo Chiquitto
2011-04-01 14:27 ` David Howells
2011-08-03 14:16 ` Leonardo Chiquitto
2011-04-01 4:38 ` Ian Kent
2011-04-01 12:13 ` Leonardo Chiquitto
2013-03-26 12:56 ` toto
2013-03-26 20:41 ` Leonardo Chiquitto
2013-03-27 0:13 ` Guillaume Apostoly
2013-03-27 4:06 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2011-03-30 16:19 Leonardo Chiquitto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1301632038.2880.11.camel@perseus \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=dhowells@redhat.com \
--cc=leonardo.lists@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.