From: Eric Paris <eparis@redhat.com>
To: Vasily Novikov <vasily.novikov@kaspersky.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@sophos.com>,
"malware-list@dmesg.printk.net" <malware-list@dmesg.printk.net>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [malware-list] A few concerns about fanotify implementation.
Date: Wed, 27 Oct 2010 11:58:54 -0400 [thread overview]
Message-ID: <1288195134.2655.202.camel@localhost.localdomain> (raw)
In-Reply-To: <1288169699.7715.103.camel@novikov-v>
On Wed, 2010-10-27 at 12:54 +0400, Vasily Novikov wrote:
> > > 3. I read the discussion about how to define paths to scan but anyway.
> > > We would prefer to have global listener that was defined in the first
> > > version of the interface and mark unnecessary mount points with
> > > persistent ignore flags.
> >
> > Yeah, but according to Eric there was fierce opposition against global mode
> > and hence he dropped it. I personally think anti-global mode arguments are not
> > that solid but what can you do.
> >
> > I am pursuing another path of trying to add support for mount marks which
> > automatically propagate to sub-mounts. That way you can mark root with a mount
> > mark and when a new filesystem appears under it it will automatically inherit
> > that mark. I have a proof of concept patch which works but needs some
> > refactoring to comply with fanotify locking rules. Hopefully it will be
> > possible to do it in which case I will post it for review.
>
> It looks good. I can help you with testing the patch.
I've got about 20 patches in
http://git.infradead.org/users/eparis/notify.git/shortlog/refs/heads/for-next
Which I hope addresses everything people have been asking for (except
Tvrtko's mount point inheritance wish)
-Eric
next prev parent reply other threads:[~2010-10-27 15:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 12:13 A few concerns about fanotify implementation Vasily Novikov
2010-10-26 12:58 ` [malware-list] " Tvrtko Ursulin
2010-10-26 13:58 ` Vasily Novikov
2010-10-26 14:22 ` Tvrtko Ursulin
[not found] ` <201010261522.34157.tvrtko.ursulin-j34lQMj1tz/QT0dZR+AlfA@public.gmane.org>
2010-10-26 14:58 ` Eric Paris
2010-10-27 8:54 ` [malware-list] " Vasily Novikov
2010-10-27 15:58 ` Eric Paris [this message]
[not found] ` <1288195134.2655.202.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2011-06-03 9:43 ` Vasily Novikov
[not found] ` <4DE8ACAD.2080003-BkmlMuIjteXqlBn2x/YWAg@public.gmane.org>
2011-06-06 9:02 ` Douglas Leeder
2011-06-06 9:19 ` [malware-list] " Vasily Novikov
[not found] ` <4DEC9B86.6060506-BkmlMuIjteXqlBn2x/YWAg@public.gmane.org>
2011-06-06 13:43 ` Eric Paris
2011-06-06 14:42 ` [malware-list] " Vasily Novikov
[not found] ` <4DECE76E.4060507-BkmlMuIjteXqlBn2x/YWAg@public.gmane.org>
2011-06-06 15:53 ` Eric Paris
2011-06-07 12:35 ` [malware-list] " Vasily Novikov
[not found] ` <C511438CDC161C41B3C47B91D99ABA8D37B4B42114-u5UUZ0l8pcxUerCGrXd8jcc3qqyFMPEu@public.gmane.org>
2011-06-06 9:42 ` Vasily Novikov
2011-06-06 10:27 ` [malware-list] " Lino Sanfilippo
2011-06-06 11:17 ` [malware-list] A few concerns about fanotify implementation ([PATCH] inside) Lino Sanfilippo
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=1288195134.2655.202.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=malware-list@dmesg.printk.net \
--cc=tvrtko.ursulin@sophos.com \
--cc=vasily.novikov@kaspersky.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;
as well as URLs for NNTP newsgroup(s).