| 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
| ||
|
Message-Id: <200706220117.09966.arnd@arndb.de> Date: Fri, 22 Jun 2007 01:17:09 +0200 From: Arnd Bergmann <arnd@...db.de> To: "C. Scott Ananian" <cscott@...top.org> Cc: linux-kernel@...r.kernel.org Subject: Re: inotify and /proc? On Thursday 21 June 2007, C. Scott Ananian wrote: > > I'd like to make a read-only /proc file which supports inotify -- that > is, the kernel can send change notifications to userland via the > inotify mechanism. I've found fsnotify_modify() (in > include/linux/fsnotify.h) which seems to do what I want, but it takes > a struct dentry * -- how can I get a dentry from a struct > proc_dir_entry and increment its ref count to keep it around? Any > help would be appreciated. Thanks! It sounds a little fishy to want that in the first place. If we wanted inotify on /proc, it should work on all files I guess, but that's an immense amount of work. What file are you talking about in particular? Why does it have to be in /proc? Why not use another notification mechanism -- blocking read(), poll(), uevent, ...? Arnd <>< - 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/
Powered by blists - more mailing lists