From: Jacob A <jacoba51-tmp@yahoo.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Al Viro <viro@ftp.linux.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.4 Q: list of open files per inode?
Date: Sun, 22 Jul 2007 05:26:19 -0700 (PDT) [thread overview]
Message-ID: <35493.81201.qm@web57701.mail.re3.yahoo.com> (raw)
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
--
next reply other threads:[~2007-07-22 12:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 12:26 Jacob A [this message]
2007-07-22 12:28 ` 2.4 Q: list of open files per inode? Jan Engelhardt
-- 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 11:39 Jacob A
2007-07-22 11:58 ` Jan Engelhardt
2007-07-22 12:51 ` Al Viro
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=35493.81201.qm@web57701.mail.re3.yahoo.com \
--to=jacoba51-tmp@yahoo.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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