From: Giuseppe Scrivano <gscrivano@gnu.org>
To: Eric Paris <eparis@parisplace.org>
Cc: linux-kernel@vger.kernel.org, bug-coreutils@gnu.org
Subject: Re: extend inotify to support file descriptors in addition to paths
Date: Fri, 11 Sep 2009 13:39:38 +0200 [thread overview]
Message-ID: <87k505bthh.fsf@master.homenet> (raw)
In-Reply-To: <7e0fb38c0909100727t51d3d523o403e05a225881403@mail.gmail.com> (Eric Paris's message of "Thu, 10 Sep 2009 10:27:25 -0400")
Eric Paris <eparis@parisplace.org> writes:
> On Tue, Sep 8, 2009 at 8:21 PM, Giuseppe Scrivano <gscrivano@gnu.org> wrote:
>
>> at the moment inotify permits to add new files to be watched using their
>> path. There are situations where the file path is not know but a
>> descriptor is available. It would be desiderable to have the
>> possibility to use the inotify system even in these (rare) cases.
>
> I don't think specifying the inode in question by fd is fundamentally
> a bad idea. It is the reason I decided to use fd's when registering
> event's in the upcoming fanotify rather than pathnames. I do however
> question if we really want to add yet another syscall for inotify.
> We've already seen that inotify is very hard to expand. The fixed
> message length, lack of information a number of users want, and
> difficultly in extending those things make me reticent to support more
> extentions.
> Personally I'd rather see us/you move to fanotify which is (I hope)
> extensible forever. If only I could get networking people to review
> it. Have you looked at fanotify? I'm going to repost the series in a
> couple minutes, maybe you could tell me if fanotify might work for
> you?
Sure, I'll take a look at it. I have few questions before look at
details: is it an attempt to replace inotify? Does fanotify use only
fd? Have the possibility to watch a file by its path, like inotify
does, is not a bad idea when the file is not already opened.
Thanks,
Giuseppe
prev parent reply other threads:[~2009-09-11 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 0:21 extend inotify to support file descriptors in addition to paths Giuseppe Scrivano
2009-09-10 14:27 ` Eric Paris
2009-09-11 11:39 ` Giuseppe Scrivano [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=87k505bthh.fsf@master.homenet \
--to=gscrivano@gnu.org \
--cc=bug-coreutils@gnu.org \
--cc=eparis@parisplace.org \
--cc=linux-kernel@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 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.