From: Henry Wilson <henry.wilson@acentic.com>
To: Jan Kara <jack@suse.cz>
Cc: amir73il@gmail.com, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v3 4.17] inotify: Add flag IN_EXCL_ADD for inotify_add_watch()
Date: Wed, 30 May 2018 14:35:13 +0100 [thread overview]
Message-ID: <470ddceb-fa27-7467-c6ad-1aca4c551432@acentic.com> (raw)
In-Reply-To: <20180530130136.uaj7akyuyp44mg3c@quack2.suse.cz>
On 30/05/18 14:01, Jan Kara wrote:
> Thanks. The patch looks good. I've added it to my tree. BTW, do you plan on
> working on a similar addition to fanotify?
>
> Honza
>
Ah that's grand, I'm glad to have helped to improve things.
I'm not familiar with fanotify, however a quick look at fanotify_user.c
suggests that a similar approach may be taken by modifying:
if(!fsn_mark) {
...
}
else if (create) {
return -EEXIST;
}
in both fanotify_add_vfsmount_mark() and fanotify_add_inode_mark()
Regards, Henry.
next prev parent reply other threads:[~2018-05-30 13:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 15:24 [PATCH 4.17] inotify: Add flag IN_ONLY_CREATE for inotify_add_watch() Henry Wilson
2018-05-03 19:42 ` Amir Goldstein
2018-05-04 8:44 ` Henry Wilson
2018-05-16 10:44 ` [PATCH v2 4.17] From: Henry Wilson <henry.wilson@acentic.com> henry.wilson
2018-05-29 9:15 ` Jan Kara
2018-05-29 11:03 ` Henry Wilson
2018-05-29 12:15 ` Jan Kara
2018-05-30 11:00 ` Henry Wilson
2018-05-30 10:26 ` [PATCH v3 4.17] inotify: Add flag IN_EXCL_ADD for inotify_add_watch() henry.wilson
2018-05-30 13:01 ` Jan Kara
2018-05-30 13:35 ` Henry Wilson [this message]
2018-05-30 15:40 ` Amir Goldstein
2018-05-30 16:04 ` Jan Kara
2018-05-30 19:03 ` Amir Goldstein
2018-05-31 9:42 ` Jan Kara
2018-05-31 8:22 ` Henry Wilson
2018-05-31 10:24 ` Amir Goldstein
2018-05-30 16:10 ` Randy Dunlap
2018-05-31 9:43 ` [PATCH v4 4.17] inotify: Add flag IN_MASK_CREATE " henry.wilson
2018-05-31 10:38 ` Amir Goldstein
2018-05-31 11:43 ` Jan Kara
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=470ddceb-fa27-7467-c6ad-1aca4c551432@acentic.com \
--to=henry.wilson@acentic.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 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).