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: Wed, 25 Jan 2017 16:42:34 +0200 [thread overview]
Message-ID: <87r33rryjp.fsf@drapion.f-secure.com> (raw)
In-Reply-To: <CAOQ4uxg6hDdgKhw6DZ2CUEf1e=PMx0t83RG-EaGLWDKf6MWUrQ@mail.gmail.com> (Amir Goldstein's message of "Wed, 25 Jan 2017 16:11:06 +0200")
Amir Goldstein <amir73il@gmail.com>:
> On Wed, Jan 25, 2017 at 4:06 PM, Marko Rauhamaa
> <marko.rauhamaa@f-secure.com> wrote:
>> Amir Goldstein <amir73il@gmail.com>:
> So I am confused.
> Your test program sets a watch on permission events on the mount
> and does not respond to permission events on the mount, so all
> file system operations on the mount SHOULD be blocked.
> What am I missing?
The problem is that the fanotify_mark() system call is hanging and as a
side effect blocks everything.
The side effect is probably completely understandable, but
fanotify_mark() should never hang, should it?
Marko
--
+358 44 990 4795
Skype: marko.rauhamaa_f-secure
next prev parent reply other threads:[~2017-01-25 14:42 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 [this message]
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
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=87r33rryjp.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.