From: Thomas Ogrisegg <tom-lkml@lkml.fnord.at>
To: linux-kernel@vger.kernel.org
Cc: rml@novell.com
Subject: [PATCH] procfs fixes for inotify/dnotify
Date: Tue, 21 Feb 2006 22:16:23 +0100 [thread overview]
Message-ID: <20060221211623.GA26413@rescue.iwoars.net> (raw)
Problem description:
When a new process is created, the creation of the respective PID
subdirectory of /proc is deferred until the /proc-directory is beeing
read (by e.g. ps(1)). This causes file notification frameworks like
dnotify and inotify to not work correctly with /proc.
This patch fixes the problem.
Signed-off-by: Thomas Ogrisegg <tom-lkml@lkml.fnord.at>
next reply other threads:[~2006-02-21 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 21:16 Thomas Ogrisegg [this message]
2006-02-21 21:18 ` [PATCH] procfs fixes for inotify/dnotify Thomas Ogrisegg
2007-07-19 22:03 ` Andrew Morton
2007-07-20 4:52 ` Alexey Dobriyan
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=20060221211623.GA26413@rescue.iwoars.net \
--to=tom-lkml@lkml.fnord.at \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.com \
/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