All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/1] fanotify.7: clarify effects of file moves
Date: Fri, 07 Aug 2015 11:18:09 +0200	[thread overview]
Message-ID: <55C477D1.1050808@gmail.com> (raw)
In-Reply-To: <1438894183-3979-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>

On 08/06/2015 10:49 PM, Heinrich Schuchardt wrote:
> If files or directories are moved to other mounts the inode is
> deleted. Fanotify marks are lost.

Thanks, Heinrich. Applied.

Cheers,

Michael


> Signed-off-by: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
> ---
>  man7/fanotify.7 | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/man7/fanotify.7 b/man7/fanotify.7
> index 54b1ea6..f63fb51 100644
> --- a/man7/fanotify.7
> +++ b/man7/fanotify.7
> @@ -91,10 +91,10 @@ ignore mask and the file cache entry can be updated.
>  .PP
>  The entries in the fanotify notification groups refer to files and
>  directories via their inode number and to mounts via their mount ID.
> -If files or directories are renamed or moved,
> +If files or directories are renamed or moved within the same mount,
>  the respective entries survive.
> -If files or directories are deleted or mounts are unmounted,
> -the corresponding entries are deleted.
> +If files or directories are deleted or moved to another mount or if mounts are
> +unmounted, the corresponding entries are deleted.
>  .SS The event queue
>  As events occur on the filesystem objects monitored by a notification group,
>  the fanotify system generates events that are collected in a queue.
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2015-08-07  9:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06 20:49 [PATCH 1/1] fanotify.7: clarify effects of file moves Heinrich Schuchardt
     [not found] ` <1438894183-3979-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2015-08-07  9:18   ` Michael Kerrisk (man-pages) [this message]

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=55C477D1.1050808@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=xypron.glpk-Mmb7MZpHnFY@public.gmane.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.