From: Arnd Bergmann <arnd@arndb.de>
To: "C. Scott Ananian" <cscott@laptop.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: inotify and /proc?
Date: Fri, 22 Jun 2007 01:17:09 +0200 [thread overview]
Message-ID: <200706220117.09966.arnd@arndb.de> (raw)
In-Reply-To: <c6d9bea0706211254r6d457e36wfb3722880a3b4abd@mail.gmail.com>
On Thursday 21 June 2007, C. Scott Ananian wrote:
>
> I'd like to make a read-only /proc file which supports inotify -- that
> is, the kernel can send change notifications to userland via the
> inotify mechanism. I've found fsnotify_modify() (in
> include/linux/fsnotify.h) which seems to do what I want, but it takes
> a struct dentry * -- how can I get a dentry from a struct
> proc_dir_entry and increment its ref count to keep it around? Any
> help would be appreciated. Thanks!
It sounds a little fishy to want that in the first place. If we wanted
inotify on /proc, it should work on all files I guess, but that's
an immense amount of work.
What file are you talking about in particular?
Why does it have to be in /proc?
Why not use another notification mechanism -- blocking read(), poll(),
uevent, ...?
Arnd <><
next prev parent reply other threads:[~2007-06-21 23:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 19:54 C. Scott Ananian
2007-06-21 23:17 ` Arnd Bergmann [this message]
2007-06-22 22:51 ` C. Scott Ananian
2007-06-22 23:28 ` Al Viro
2007-06-25 3:12 ` Kyle Moffett
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=200706220117.09966.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=cscott@laptop.org \
--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
Powered by JetHome