Re: [malware-list] A few concerns about fanotify implementation.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux