[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20081006150858.GA1380@ucw.cz>
Date: Mon, 6 Oct 2008 17:09:50 +0200
From: Pavel Machek <pavel@...e.cz>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: david@...g.hm, Eric Paris <eparis@...hat.com>,
linux-kernel@...r.kernel.org, malware-list@...ts.printk.net,
arjan@...radead.org, bunk@...nel.org, tytso@....edu,
tvrtko.ursulin@...hos.com, hch@...radead.org, andi@...stfloor.org,
viro@...IV.linux.org.uk, peterz@...radead.org,
Jonathan.Press@...com, riel@...hat.com
Subject: Re: [RFC] 0/11 fanotify: fscking all notifiction and file access
system (intended for antivirus scanning and file indexers)
Hi!
> > sending a message out for every READ/WRITE seems like it will generate a
> > LOT of messages, and very few will be ones that anyone cares about.
>
> On read there isn't much point anyway, on write if you simply send one,
> save an event counter number and don't send another until the last one is
> cleared it all works well. When the last event is cleared if another
> event has occurred then the event counter will have changed so you know
> to send one immediately, if the app doesn't want to receive them for a
> while it can just hang onto the event for a minute or two before clearing
> it.
Actually both read and write seems useless, as both can be bypassed by
mmap...?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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