From: Marko Rauhamaa <marko.rauhamaa@f-secure.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: Reproducible, long-standing fanotify+autofs problem
Date: Thu, 26 Jan 2017 19:47:54 +0200 [thread overview]
Message-ID: <87sho5r9v9.fsf@drapion.f-secure.com> (raw)
In-Reply-To: <87inp3rwsy.fsf@drapion.f-secure.com> (Marko Rauhamaa's message of "Wed, 25 Jan 2017 17:20:13 +0200")
Marko Rauhamaa <marko.rauhamaa@f-secure.com>:
> Amir Goldstein <amir73il@gmail.com>:
> I have narrowed the problem down a bit in the kernel. The hanging
> function is "user_path_at":
>
> user_path_at(filename="/sshome/test/user/", lookup_flags=0x1)
> called from: fanotify_find_path()
> called from: fanotify_mark()
>
> And Ctrl-C wakes it up.
I have dug a bit deeper. What hangs is this statement:
mnt = path->dentry->d_op->d_automount(path);
in:
follow_automount() // fs/namei.c
called from: follow_managed()
called from: walk_component()
called from: lookup_last()
called from: path_lookupat()
called from: filename_lookup()
called from: user_path_at_empty()
called from: user_path_at(filename="/sshome/test/user/", lookup_flags=0x1)
called from: fanotify_find_path() // fs/notify/fanotify_user.c
called from: fanotify_mark()
And Ctrl-C wakes it up.
The d_automount() method is bound to autofs4_d_automount() in
fs/autofs4/root.c. The hanging statement is:
wait_event_interruptible(wq->queue, wq->name.name == NULL);
in:
autofs4_wait() // fs/autofs4/waitq.c
called from: autofs4_mount_wait() // fs/autofs4/root.c
called from: autofs4_d_automount()
Marko
--
+358 44 990 4795
Skype: marko.rauhamaa_f-secure
next prev parent reply other threads:[~2017-01-26 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 11:48 Reproducible, long-standing fanotify+autofs problem Marko Rauhamaa
2017-01-25 12:03 ` Amir Goldstein
2017-01-25 14:06 ` Marko Rauhamaa
2017-01-25 14:11 ` Amir Goldstein
2017-01-25 14:42 ` Marko Rauhamaa
2017-01-25 14:54 ` Amir Goldstein
2017-01-25 15:15 ` Jan Kara
[not found] ` <87efzrrwec.fsf@drapion.f-secure.com>
[not found] ` <20170127134620.GA16757@quack2.suse.cz>
2017-01-27 14:21 ` Marko Rauhamaa
2017-01-25 15:20 ` Marko Rauhamaa
2017-01-26 17:47 ` Marko Rauhamaa [this message]
2017-01-26 18:05 ` Marko Rauhamaa
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=87sho5r9v9.fsf@drapion.f-secure.com \
--to=marko.rauhamaa@f-secure.com \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
/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.