public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <zbr@ioremap.net>
To: Jamie Lokier <jamie@shareable.org>
Cc: Eric Paris <eparis@redhat.com>,
	david@lang.hm, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, malware-list@dmesg.printk.net,
	Valdis.Kletnieks@vt.edu, greg@kroah.com, jcm@redhat.com,
	douglas.leeder@sophos.com, tytso@mit.edu, arjan@infradead.org,
	jengelh@medozas.de, aviro@redhat.com, mrkafk@gmail.com,
	alexl@redhat.com, jack@suse.cz, tvrtko.ursulin@sophos.com,
	a.p.zijlstra@chello.nl, hch@infradead.org,
	alan@lxorguk.ukuu.org.uk, mmorley@hcl.in
Subject: Re: fanotify - overall design before I start sending patches
Date: Mon, 27 Jul 2009 21:52:25 +0400	[thread overview]
Message-ID: <20090727175225.GA27999@ioremap.net> (raw)
In-Reply-To: <20090724214401.GJ27755@shareable.org>

Hi.

On Fri, Jul 24, 2009 at 10:44:01PM +0100, Jamie Lokier (jamie@shareable.org) wrote:
> > No, I will NOT EVER pass a pathname.  Period.  End of story.  I stated
> > the if userspace wants to deal with pathnames (and they understand the
> > system setup well enough to know if pathnames even make sense to them)
> > they can use readlink(2) on /proc/self/fd
> 
> That makes sense.
> 
> In most cases where events trigger userspace cache or index updates,
> userspace already has enough information to calculate the path (and
> any derived data) from the inode number (in the case of non-hard-link
> files) or from the inode number of the parent directory and the name
> (not full path).

Except that rlimits may forbid to open new file descriptor while queue
length is enough to put another event with the full or partial path
name.

I will read initial mail next, but if it is not described there, how
rlimit problem is handled?

-- 
	Evgeniy Polyakov

  reply	other threads:[~2009-07-27 17:52 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-24 20:13 fanotify - overall design before I start sending patches Eric Paris
2009-07-24 20:48 ` david
2009-07-24 21:01   ` Eric Paris
2009-07-24 21:44     ` Jamie Lokier
2009-07-27 17:52       ` Evgeniy Polyakov [this message]
2009-07-29 20:11         ` Eric Paris
2009-07-24 21:00 ` Andreas Dilger
2009-07-24 21:21   ` Eric Paris
2009-07-24 22:42     ` Andreas Dilger
2009-07-24 23:01       ` Jamie Lokier
2009-07-24 22:48 ` Jamie Lokier
2009-07-24 23:25   ` Eric Paris
2009-07-24 23:46     ` Jamie Lokier
2009-07-24 23:49   ` Eric Paris
2009-07-25  0:29     ` Jamie Lokier
2009-07-27 18:33       ` Andreas Dilger
2009-07-27 19:23         ` Jamie Lokier
2009-07-28 17:59           ` Andreas Dilger
2009-07-29 20:14           ` Eric Paris
2009-07-29 20:12         ` Eric Paris
2009-07-29 20:07       ` Eric Paris
2009-07-27 16:54   ` Jan Kara
2009-07-25 14:22 ` Niraj kumar
2009-07-29 20:08   ` Eric Paris
2009-07-28 11:48 ` Jon Masters
2009-07-29 20:20   ` Eric Paris
2009-08-03 16:23 ` Christoph Hellwig
2009-08-03 16:55   ` Eric Paris
2009-08-03 18:04     ` Christoph Hellwig
2009-08-03 18:13       ` Eric Paris
2009-08-04 16:09 ` Tvrtko Ursulin
2009-08-04 16:27   ` Eric Paris
2009-08-04 16:39     ` Tvrtko Ursulin
2009-08-04 17:22     ` Valdis.Kletnieks
2009-08-04 18:20       ` John Stoffel
2009-08-04 18:50         ` Eric Paris
2009-08-05  9:32         ` Tvrtko Ursulin
2009-08-04 16:34 ` Tvrtko Ursulin
2009-08-05 10:12   ` Douglas Leeder
2009-08-05 10:35   ` Douglas Leeder
2009-08-05  2:05 ` Pavel Machek
2009-08-05 16:46   ` Tvrtko Ursulin
2009-08-06 10:10     ` Pavel Machek
2009-08-06 10:20       ` Tvrtko Ursulin
2009-08-06 10:24         ` Pavel Machek
2009-08-06 10:20       ` Douglas Leeder
2009-08-06 10:22         ` Pavel Machek
2009-08-07  8:59           ` Jamie Lokier
2009-08-06 10:29         ` Peter Zijlstra
2009-08-06 10:59           ` Tvrtko Ursulin
2009-08-06 11:23             ` Peter Zijlstra
2009-08-06 12:48               ` Tvrtko Ursulin
2009-08-06 12:58                 ` Alan Cox
2009-08-06 18:18                   ` Eric Paris
2009-08-06 13:50               ` Kernel Event Notification Subsystem (was: fanotify - overall design before I start sending patches) Al Boldi
2009-08-06 18:18               ` fanotify - overall design before I start sending patches Eric Paris
2009-08-07 16:36                 ` Miklos Szeredi
2009-08-07 17:43                   ` Eric Paris
2009-08-08 10:36                     ` Pavel Machek
2009-08-10 10:03                     ` Miklos Szeredi
2009-08-08 10:34                 ` Pavel Machek
2009-08-06 11:24             ` Pavel Machek

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=20090727175225.GA27999@ioremap.net \
    --to=zbr@ioremap.net \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=alexl@redhat.com \
    --cc=arjan@infradead.org \
    --cc=aviro@redhat.com \
    --cc=david@lang.hm \
    --cc=douglas.leeder@sophos.com \
    --cc=eparis@redhat.com \
    --cc=greg@kroah.com \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=jamie@shareable.org \
    --cc=jcm@redhat.com \
    --cc=jengelh@medozas.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=malware-list@dmesg.printk.net \
    --cc=mmorley@hcl.in \
    --cc=mrkafk@gmail.com \
    --cc=tvrtko.ursulin@sophos.com \
    --cc=tytso@mit.edu \
    /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