Messages in this thread | | | Date | Sun, 22 Jul 2007 05:45:06 -0700 (PDT) | From | Jacob A <> | Subject | Re: 2.4 Q: list of open files per inode? |
| |
Ah, yes, this was my intention, to keep the state in filp->private_data. But then at a timer routine I wanted to go over all the filps associated with the device and check/modify the state. That's why I needed the open files list. -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 3:28:30 PM Subject: Re: 2.4 Q: list of open files per inode?
On Jul 22 2007 05:26, Jacob A wrote:
>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 --
>
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/
| |