public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: John Stoffel <john@stoffel.org>
Cc: Tvrtko Ursulin <tvrtko.ursulin@sophos.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	agruen@suse.de
Subject: Re: Linux 2.6.36-rc7
Date: Thu, 07 Oct 2010 17:24:34 -0400	[thread overview]
Message-ID: <1286486674.2571.16.camel@localhost.localdomain> (raw)
In-Reply-To: <19630.13234.840343.153381@quad.stoffel.home>

On Thu, 2010-10-07 at 16:55 -0400, John Stoffel wrote:

> So what happens when you try to register a priority level and someone
> else has already gotten that level?  Does the call fail?  Do you get
> bumped down to the next open level?  Can you *tell* what level you're
> at and whether or not some other decision maker is ahead of you? 

Well it hasn't been discussed and implemented so I can't answer that.
*smile*

I will tell you that the way I envision it working (and being backwards
compatible) is that priority 0 is the last thing to be serviced.  If 2
things register at the same priority the order between them getting
events is unpredictable.  So when an HSM uses the interface it would use
the highest priority.  An AV vendor might use (highest priority / 2)
while normal inotify like listeners would all be happy using priority 0.

> But I'd really like some docs in the next release which tells me as a
> poor dumb sysadmin how it can and should be used and what the gotchas
> are.

We have example man-like pages in the commit logs which I expected to be
used as the basis for man pages once the interface was accepted.  They
aren't perfect but they are

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=52c923dd079df49f58016a9e56df184b132611d6
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=2a3edf86040a7e15684525a2aadc29f532c51325

You'll also find an example program which shows all of the features at

http://git.kernel.org/?p=linux/kernel/git/agruen/fanotify-example.git;a=summary

I don't think digging around in kernel code is the right way   :)

-Eric


  reply	other threads:[~2010-10-07 21:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06 21:45 Linux 2.6.36-rc7 Linus Torvalds
2010-10-07  0:49 ` Stephen Rothwell
2010-10-08 15:05   ` James Bottomley
2010-10-07 16:10 ` Tvrtko Ursulin
2010-10-07 17:15   ` Tvrtko Ursulin
2010-10-07 17:33     ` Eric Paris
2010-10-07 18:07       ` Alan Cox
2010-10-07 17:49         ` Eric Paris
2010-10-08 12:06           ` Andreas Gruenbacher
2010-10-08 16:33             ` David Daney
2010-10-08 21:50               ` Andreas Gruenbacher
2010-10-08 21:59                 ` H. Peter Anvin
2010-10-11 22:13                   ` fanotify: disable fanotify syscalls Eric Paris
2010-10-08 16:38             ` Linux 2.6.36-rc7 Eric Paris
2010-10-08 21:45               ` Andreas Gruenbacher
2010-10-07 20:55       ` John Stoffel
2010-10-07 21:24         ` Eric Paris [this message]
2010-10-08 15:42           ` John Stoffel
2010-10-08 16:17             ` Tvrtko Ursulin
2010-10-08 16:41               ` Eric Paris
2010-10-18 11:01                 ` Tvrtko Ursulin
2010-10-08 16:54               ` John Stoffel
2010-10-08 21:03               ` Andreas Gruenbacher
2010-10-09  0:46                 ` John Stoffel
2010-10-07 19:28 ` Tejun Heo
2010-10-07 20:13   ` [dm-devel] " Milan Broz
2010-10-08 17:02     ` Tejun Heo
2010-10-10 11:56       ` Torsten Kaiser
2010-10-11 10:09       ` [PATCH wq#for-next] workqueue: fix HIGHPRI handling in keep_working() Tejun Heo

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=1286486674.2571.16.camel@localhost.localdomain \
    --to=eparis@redhat.com \
    --cc=agruen@suse.de \
    --cc=john@stoffel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tvrtko.ursulin@sophos.com \
    /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