From: Al Viro <viro@ftp.linux.org.uk>
To: Jacob A <jacoba51-tmp@yahoo.com>
Cc: Jan Engelhardt <jengelh@computergmbh.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.4 Q: list of open files per inode?
Date: Sun, 22 Jul 2007 13:51:20 +0100 [thread overview]
Message-ID: <20070722125120.GY21668@ftp.linux.org.uk> (raw)
In-Reply-To: <259547.37103.qm@web57705.mail.re3.yahoo.com>
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
next prev parent reply other threads:[~2007-07-22 12:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 11:39 2.4 Q: list of open files per inode? Jacob A
2007-07-22 11:58 ` Jan Engelhardt
2007-07-22 12:51 ` Al Viro [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-22 12:45 Jacob A
2007-07-22 13:07 ` Jan Engelhardt
2007-07-22 14:35 ` Al Viro
2007-07-22 12:26 Jacob A
2007-07-22 12:28 ` Jan Engelhardt
2007-07-19 9:01 Jacob A
2007-07-19 11:41 ` Jan Engelhardt
2007-07-19 16:38 ` Al Viro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070722125120.GY21668@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=jacoba51-tmp@yahoo.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox