linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Murphy Zhou <jencce.kernel@gmail.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>, Jan Kara <jack@suse.cz>,
	Linux-Fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-unionfs@vger.kernel.org
Subject: Re: [PATCH v2] ovl: do not generate duplicate fsnotify events for "fake" path
Date: Sun, 28 Apr 2019 11:08:52 +0800	[thread overview]
Message-ID: <CADJHv_tDBdHNBqrO_uARQhMZYEeadPcoshtXFVnvpcVpOFGdhQ@mail.gmail.com> (raw)
In-Reply-To: <20190424163950.14123-1-amir73il@gmail.com>

On Thu, Apr 25, 2019 at 12:39 AM Amir Goldstein <amir73il@gmail.com> wrote:
>
> Overlayfs "fake" path is used for stacked file operations on
> underlying files.  Operations on files with "fake" path must not
> generate fsnotify events with path data, because those events have
> already been generated at overlayfs layer and because the reported
> event->fd for fanotify marks on underlying inode/filesystem will
> have the wrong path (the overlayfs path).
>
> Link: https://lore.kernel.org/linux-fsdevel/20190423065024.12695-1-jencce.kernel@gmail.com/
> Reported-by: Murphy Zhou <jencce.kernel@gmail.com>
> Fixes: d1d04ef8572b ("ovl: stack file ops")
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> ---
>
> Miklos,
>
> V1 was addressed to Jan and was trying to teach fsnotify about fake path.
> V2 leaves fsnotify subsystem alone and just sets the FMODE_NONOTIFY
> flag on realfile. All the rest of the complications with mark mounts
> are irrelevant.
>
> Same extended fanotify06 that was used to verify V1 also verified V2.

Thanks for fixing this!

My overlayfs tests on this patch looks good.

M

>
> Thanks,
> Amir.
>
>  fs/overlayfs/file.c | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/fs/overlayfs/file.c b/fs/overlayfs/file.c
> index ddfd93f13cc5..7d2f01957e40 100644
> --- a/fs/overlayfs/file.c
> +++ b/fs/overlayfs/file.c
> @@ -29,10 +29,11 @@ static struct file *ovl_open_realfile(const struct file *file,
>         struct inode *inode = file_inode(file);
>         struct file *realfile;
>         const struct cred *old_cred;
> +       int flags = file->f_flags | O_NOATIME | FMODE_NONOTIFY;
>
>         old_cred = ovl_override_creds(inode->i_sb);
> -       realfile = open_with_fake_path(&file->f_path, file->f_flags | O_NOATIME,
> -                                      realinode, current_cred());
> +       realfile = open_with_fake_path(&file->f_path, flags, realinode,
> +                                      current_cred());
>         revert_creds(old_cred);
>
>         pr_debug("open(%p[%pD2/%c], 0%o) -> (%p, 0%o)\n",
> @@ -50,7 +51,7 @@ static int ovl_change_flags(struct file *file, unsigned int flags)
>         int err;
>
>         /* No atime modificaton on underlying */
> -       flags |= O_NOATIME;
> +       flags |= O_NOATIME | FMODE_NONOTIFY;
>
>         /* If some flag changed that cannot be changed then something's amiss */
>         if (WARN_ON((file->f_flags ^ flags) & ~OVL_SETFL_MASK))
> --
> 2.17.1
>

  parent reply	other threads:[~2019-04-28  3:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 16:39 [PATCH v2] ovl: do not generate duplicate fsnotify events for "fake" path Amir Goldstein
2019-04-25  0:55 ` kbuild test robot
2019-04-28  3:08 ` Murphy Zhou [this message]
2019-05-06 11:58   ` Miklos Szeredi

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=CADJHv_tDBdHNBqrO_uARQhMZYEeadPcoshtXFVnvpcVpOFGdhQ@mail.gmail.com \
    --to=jencce.kernel@gmail.com \
    --cc=amir73il@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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).