lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1286486674.2571.16.camel@localhost.localdomain>
Date:	Thu, 07 Oct 2010 17:24:34 -0400
From:	Eric Paris <eparis@...hat.com>
To:	John Stoffel <john@...ffel.org>
Cc:	Tvrtko Ursulin <tvrtko.ursulin@...hos.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	agruen@...e.de
Subject: Re: Linux 2.6.36-rc7

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ