linux-kernel - Re: [GIT PULL] notification tree: directory events

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 18 Aug 2010 17:47:14 +0200
From:	Andreas Gruenbacher <agruen@...e.de>
To:	Eric Paris <eparis@...hat.com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Matt Helsley <matthltc@...ibm.com>,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	viro@...iv.linux.org.uk, akpm@...ux-foundation.org,
	Michael Kerrisk <michael.kerrisk@...il.com>
Subject: Re: [GIT PULL] notification tree: directory events

Eric,

one more thing that doesn't make sense is events on directories: when watching 
a directory, some actions like reading a directory or creat()ing a file in the 
directory will generate events (even open_perm and access_perm), but other 
actions like hard linking files into the directory or removing files will not 
create any events.  This means that fanotify currently cannot be used for 
watching for directory changes.

In my opinion, events on directories should either be made to actually work, 
or else no directory events at all should be generated.

Also, I can think of users of fanotify which are not concerned with directory 
events at all.  It would make sense to allow such users to subscribe only to 
file events and not receive any directory events which they will end up 
ignoring anyway.

Again it shows that this code just wasn't ready to be merged yet ...

Andreas
--
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/