From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: mtk.manpages@gmail.com
Cc: Mike Frysinger <vapier@gentoo.org>,
linux-man@vger.kernel.org, viro@zeniv.linux.org.uk,
Richard Weinberger <richard@nod.at>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] open(2): document O_PATH
Date: Thu, 03 May 2012 19:34:35 +0530 [thread overview]
Message-ID: <87bom5xswc.fsf@skywalker.in.ibm.com> (raw)
In-Reply-To: <CAKgNAkiRH8p=Dp1tqkb3D9oRVCOSnj2bofgFN5x2svntN7vtPg@mail.gmail.com>
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com> writes:
> Aneesh,
>
>>
>> I don't know much about markers, but as per fsnotify_backend.h
>>
>> /*
>> * a mark is simply an object attached to an in core inode which allows an
>> * fsnotify listener to indicate they are either no longer interested in events
>> * of a type matching mask or only interested in those events.
>> *
>> * these are flushed when an inode is evicted from core and may be flushed
>> * when the inode is modified (as seen by fsnotify_access). Some fsnotify users
>> * (such as dnotify) will flush these when the open fd is closed and not at
>> * inode eviction or modification.
>> */
>> struct fsnotify_mark {
>
> Unfortunately, I'm still none the wiser about what this means for
> O_PATH file descriptors...
>
I looked at dnotify_flush, they remove markers on an inode.
But then it also checks for filp to match. So I am not sure
whether skipping dnotify_flush for O_PATH descriptor have any impact. We
can't use O_PATH descriptor for dnotify fcntl any way. So in
dnotify_flush we will not match the filp.
Viro,
Any reason why we skip dnotify_flush ?
-aneesh
next prev parent reply other threads:[~2012-05-03 14:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1335669917-23970-1-git-send-email-vapier@gentoo.org>
2012-04-29 21:39 ` [PATCH] open(2): document O_PATH Michael Kerrisk (man-pages)
2012-04-30 7:39 ` Aneesh Kumar K.V
2012-04-30 11:44 ` Ted Ts'o
2012-05-03 6:48 ` Michael Kerrisk (man-pages)
2012-05-03 8:27 ` Aneesh Kumar K.V
2012-05-03 13:07 ` Ted Ts'o
2012-05-03 13:20 ` Al Viro
2012-05-06 1:00 ` H. Peter Anvin
2012-05-03 6:47 ` Michael Kerrisk (man-pages)
2012-05-03 14:04 ` Aneesh Kumar K.V [this message]
2012-05-03 14:11 ` Al Viro
2012-05-05 11:31 ` Michael Kerrisk (man-pages)
2013-01-08 18:52 ` Al Viro
2013-03-14 9:35 Michael Kerrisk (man-pages)
2013-07-20 11:40 ` Al Viro
2013-07-20 20:56 ` Michael Kerrisk
2013-07-22 8:46 ` Peter Schiffer
2013-07-22 10:45 ` Michael Kerrisk (man-pages)
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=87bom5xswc.fsf@skywalker.in.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=richard@nod.at \
--cc=vapier@gentoo.org \
--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).