linux-kernel - Re: [PATCH -v3 5/8] fsnotify: unified filesystem notification backend

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20081128045446.GG28946@ZenIV.linux.org.uk>
Date:	Fri, 28 Nov 2008 04:54:46 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Eric Paris <eparis@...hat.com>
Cc:	linux-kernel@...r.kernel.org, malware-list@...ts.printk.net,
	akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk,
	arjan@...radead.org, hch@...radead.org, a.p.zijlstra@...llo.nl
Subject: Re: [PATCH -v3 5/8] fsnotify: unified filesystem notification
	backend

On Tue, Nov 25, 2008 at 12:21:18PM -0500, Eric Paris wrote:

What the hell is ->notification_list and what in this patchset would
add stuff to it?  Even more interesting question: how long would these
guys remain there and what's to prevent a race with umount?  At least
'inode-only' events will pin down the inode and leaving the matching
iput() until after umount() is a Bad Thing(tm)...
--
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/