From: Valdis.Kletnieks@vt.edu
To: trelane@digitasaru.net
Cc: Al Viro <viro@ftp.linux.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: inotify and /proc/<pid>
Date: Tue, 31 Jul 2007 21:33:11 -0400 [thread overview]
Message-ID: <13954.1185931991@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 30 Jul 2007 22:56:27 CDT." <20070731035626.GG6812@digitasaru.net>
[-- Attachment #1: Type: text/plain, Size: 638 bytes --]
On Mon, 30 Jul 2007 22:56:27 CDT, Joseph Pingenot said:
> From Al Viro on Tuesday, 31 July, 2007:
> >On Mon, Jul 30, 2007 at 10:40:59PM -0500, Joseph Pingenot wrote:
> >> I'm trying to implement pwait. It blocks until a specified PID exits,
> >> and then it exits.
> >er... ptrace(2)?
>
> Should work for most common usage scenarios, although will suspect that it
> won't for for processes owned by another user (at least, I hope
> it wouldn't).
>
> What is dangerous about inotify on a proc file?
And if it's dangerous, should the inotify system call fail when trying to
set the watch? Bailout with a -EBADIDEA or something?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2007-08-01 1:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 2:16 Joseph Pingenot
2007-07-31 3:17 ` Al Viro
2007-07-31 3:25 ` Joseph Pingenot
2007-07-31 3:31 ` Joseph Pingenot
2007-07-31 3:36 ` Al Viro
2007-07-31 3:40 ` Joseph Pingenot
2007-07-31 3:48 ` Kyle McMartin
2007-07-31 3:50 ` Al Viro
2007-07-31 3:56 ` Joseph Pingenot
2007-07-31 4:01 ` Al Viro
2007-08-01 1:33 ` Valdis.Kletnieks [this message]
2007-07-31 5:48 ` Chris Friesen
2007-07-31 3:31 ` Al Viro
2007-07-31 15:50 ` Ray Lee
2007-07-31 18:31 ` Diego Calleja
2007-08-01 0:41 ` Andrew Morton
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=13954.1185931991@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=trelane@digitasaru.net \
--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
all inboxes | Powered by JetHome®