| 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
| ||
|
Date: Sun, 22 Jul 2007 13:51:20 +0100 From: Al Viro <viro@....linux.org.uk> To: Jacob A <jacoba51-tmp@...oo.com> Cc: Jan Engelhardt <jengelh@...putergmbh.de>, linux-kernel@...r.kernel.org Subject: Re: 2.4 Q: list of open files per inode? On Sun, Jul 22, 2007 at 04:39:14AM -0700, Jacob A wrote: > Al, > > I'm using the open/close call as a way for processes to register/unregister with a watchdog driver that I'm writing. > I thought that I can save the housekeeping within the driver, but it looks like It would be easier just to maintain my own list > and be done with it. What do you mean "register with a watchdog driver"? The process that had opened file might be long gone while the file remains open... What kind of information do you keep for each struct file? PS: stop top-posting - 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