From: Pavel Machek <pavel@suse.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: david@lang.hm, Eric Paris <eparis@redhat.com>,
linux-kernel@vger.kernel.org, malware-list@lists.printk.net,
arjan@infradead.org, bunk@kernel.org, tytso@mit.edu,
tvrtko.ursulin@sophos.com, hch@infradead.org,
andi@firstfloor.org, viro@ZenIV.linux.org.uk,
peterz@infradead.org, Jonathan.Press@ca.com, riel@redhat.com
Subject: Re: [RFC] 0/11 fanotify: fscking all notifiction and file access system (intended for antivirus scanning and file indexers)
Date: Mon, 6 Oct 2008 17:09:50 +0200 [thread overview]
Message-ID: <20081006150858.GA1380@ucw.cz> (raw)
In-Reply-To: <20080927122031.2d4dd1b0@lxorguk.ukuu.org.uk>
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
next prev parent reply other threads:[~2008-10-07 13:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 21:07 [RFC] 0/11 fanotify: fscking all notifiction and file access system (intended for antivirus scanning and file indexers) Eric Paris
2008-09-26 21:34 ` Alan Cox
2008-09-26 21:48 ` [malware-list] " Greg KH
2008-09-26 22:03 ` Eric Paris
2008-10-02 19:24 ` Eric Paris
2008-10-02 20:48 ` Alan Cox
2008-09-27 6:05 ` david
2008-09-27 11:20 ` Alan Cox
2008-10-06 15:09 ` Pavel Machek [this message]
2008-09-27 14:04 ` Eric Paris
[not found] ` <5CB739747AC639489F3E8210950C3E555C39EE@geousmail3.GEO.CORP.HCL.IN>
2008-10-07 17:36 ` [malware-list] [RFC] 0/11 fanotify: fscking all notifiction andfile access system (intended for antivirus scanning and fileindexers) Eric Paris
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=20081006150858.GA1380@ucw.cz \
--to=pavel@suse.cz \
--cc=Jonathan.Press@ca.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andi@firstfloor.org \
--cc=arjan@infradead.org \
--cc=bunk@kernel.org \
--cc=david@lang.hm \
--cc=eparis@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malware-list@lists.printk.net \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=tvrtko.ursulin@sophos.com \
--cc=tytso@mit.edu \
--cc=viro@ZenIV.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.