Messages in this thread | | | Date | Sun, 22 Jul 2007 05:26:19 -0700 (PDT) | From | Jacob A <> | Subject | Re: 2.4 Q: list of open files per inode? |
| |
I want to keep an internal state per each registration instance, and I opted to use open() as the registration mechanism. -Jacob
----- Original Message ---- From: Jan Engelhardt <jengelh@computergmbh.de> To: Jacob A <jacoba51-tmp@yahoo.com> Cc: Al Viro <viro@ftp.linux.org.uk>; linux-kernel@vger.kernel.org Sent: Sunday, July 22, 2007 2:58:18 PM Subject: Re: 2.4 Q: list of open files per inode?
On Jul 22 2007 04:39, Jacob A wrote:
>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.
Sounds a bit wrong. _What_ exactly do you want to keep?
Jan --
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |