linux-kernel - Re: Issues with using fanotify for a filesystem indexer

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: <20090327130242.GW28946@ZenIV.linux.org.uk>
Date:	Fri, 27 Mar 2009 13:02:43 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Alexander Larsson <alexl@...hat.com>
Cc:	eparis@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: Issues with using fanotify for a filesystem indexer

On Fri, Mar 27, 2009 at 01:47:23PM +0100, Alexander Larsson wrote:

> In order to write an app using the fanotify API satisfying the above
> needs we would need the following events:
> * the event queue overflowed, (you need to reindex everything)
> * An inode was linked into the filesystem (creat, O_CREAT,
> mkdir, link, symlink, etc)
> * An inode was unlinked (unlink, rmdir, rename replaced existing file)
> * An inode was moved in the filesystem (rename)

Erm...  Just how would you represent and *order* the events?  Note that
"serialize all directory operations on given fs" is a non-starter...
--
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/