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 <[email protected]>
To: Jacob A <[email protected]>
Cc: Al Viro <[email protected]>; [email protected]
Sent: Sunday, July 22, 2007 2:58:18 PM
Subject: Re: 2.4 Q: list of open files per inode?
Quoted 5 lines · Jacob A
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
Quoted 2 lines · Jacob A
I want to keep an internal state per each registration instance, and I opted to use
open()as the registration mechanism.
So why not just store it in filp->private_data?
Jan
Quoted 1 line
Jan