From: Al Viro <viro@ZenIV.linux.org.uk>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Marko Rauhamaa <marko.rauhamaa@f-secure.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Jan Kara <jack@suse.cz>, Jeff Layton <jlayton@poochiereds.net>
Subject: Re: fanotify read returns with errno == EOPENSTALE
Date: Wed, 22 Mar 2017 19:31:22 +0000 [thread overview]
Message-ID: <20170322193122.GV29622@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAOQ4uxjzjFDLmvebHmC4t4_tT8xyWfbHVGfKohEqw7ZjpxfV_w@mail.gmail.com>
On Wed, Mar 22, 2017 at 02:20:15PM -0400, Amir Goldstein wrote:
> Well, the behavior was changed in kernel 4.7 (and stable kernels) by
> commit by Al Viro:
> fac7d19 fix EOPENSTALE bug in do_last()
>
> Since that commit userspace will be able to see this error in fanotify events.
Unless *notify somehow uses do_last() directly, that commit should have
no effect on it (and it definitely has no effect on dentry_open() callers)...
next prev parent reply other threads:[~2017-03-22 19:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 15:31 fanotify read returns with errno == EOPENSTALE Marko Rauhamaa
2017-03-22 18:01 ` Matthew Wilcox
2017-03-22 18:20 ` Amir Goldstein
2017-03-22 19:17 ` Amir Goldstein
2017-03-22 19:31 ` Al Viro [this message]
2017-03-22 19:39 ` Amir Goldstein
2017-03-23 8:13 ` Marko Rauhamaa
2017-03-23 11:46 ` Amir Goldstein
2017-03-23 11:56 ` Jeff Layton
2017-03-23 12:43 ` Marko Rauhamaa
2017-03-23 13:47 ` Amir Goldstein
2017-04-19 13:46 ` Marko Rauhamaa
2017-04-20 11:06 ` Amir Goldstein
2017-04-20 11:33 ` Amir Goldstein
2017-04-20 12:43 ` Marko Rauhamaa
2017-04-20 13:34 ` Amir Goldstein
2017-04-21 13:13 ` Marko Rauhamaa
2017-04-20 14:20 ` Jan Kara
2017-04-20 15:06 ` Amir Goldstein
2017-04-22 7:22 ` Amir Goldstein
2017-04-24 7:40 ` 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=20170322193122.GV29622@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=jlayton@poochiereds.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=marko.rauhamaa@f-secure.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).