From: Jan Kara <jack@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Marko Rauhamaa <marko.rauhamaa@f-secure.com>,
Jeff Layton <jlayton@poochiereds.net>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Jan Kara <jack@suse.cz>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
linux-api@vger.kernel.org
Subject: Re: fanotify read returns with errno == EOPENSTALE
Date: Thu, 20 Apr 2017 16:20:35 +0200 [thread overview]
Message-ID: <20170420142035.GE22135@quack2.suse.cz> (raw)
In-Reply-To: <CAOQ4uxjA8Z7wnwuHFCKeKT1xz0Gh-qS40Y6cfPi3fAM0MKsRuQ@mail.gmail.com>
On Thu 20-04-17 14:33:04, Amir Goldstein wrote:
>
> Sorry I messed up the previous patch. please try this one:
>
> diff --git a/fs/notify/fanotify/fanotify_user.c
> b/fs/notify/fanotify/fanotify_user.c
> index 2b37f27..7864354 100644
> --- a/fs/notify/fanotify/fanotify_user.c
> +++ b/fs/notify/fanotify/fanotify_user.c
> @@ -295,6 +295,16 @@ static ssize_t fanotify_read(struct file *file,
> char __user *buf,
> }
>
> ret = copy_event_to_user(group, kevent, buf);
> + if (unlikely(ret == -EOPENSTALE)) {
> + /*
> + * We cannot report events with stale fd so drop it.
> + * Setting ret to 0 will continue the event loop and
> + * do the right thing if there are no more events to
> + * read (i.e. return bytes read, -EAGAIN or wait).
> + */
> + ret = 0;
> + }
> +
> /*
> * Permission events get queued to wait for response. Other
> * events can be destroyed now.
> @@ -305,7 +315,7 @@ static ssize_t fanotify_read(struct file *file,
> char __user *buf,
> break;
> } else {
> #ifdef CONFIG_FANOTIFY_ACCESS_PERMISSIONS
> - if (ret < 0) {
> + if (ret <= 0) {
> FANOTIFY_PE(kevent)->response = FAN_DENY;
> wake_up(&group->fanotify_data.access_waitq);
> break;
I don't think you want to break out of the reading loop when ret == 0 and
the code might be more readable as:
if (!(kevent->mask & FAN_ALL_PERM_EVENTS)) {
fsnotify_destroy_event(group, kevent);
} else {
#ifdef CONFIG_FANOTIFY_ACCESS_PERMISSIONS
if (ret <= 0) {
FANOTIFY_PE(kevent)->response = FAN_DENY;
wake_up(&group->fanotify_data.access_waitq);
} else {
spin_lock(&group->notification_lock);
list_add_tail(&kevent->list,
&group->fanotify_data.access_list);
spin_unlock(&group->notification_lock);
}
#endif
}
if (ret < 0)
break;
Hmm?
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2017-04-20 14:47 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
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 [this message]
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=20170420142035.GE22135@quack2.suse.cz \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=jlayton@poochiereds.net \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=marko.rauhamaa@f-secure.com \
--cc=viro@zeniv.linux.org.uk \
/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).