From: Neil Horman <nhorman@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Neil Horman <nhorman@redhat.com>, Matthew Wilcox <matthew@wil.cx>,
linux-fsdevel@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Patch][RFC] fcntl: add ability to stop monitored processes
Date: Mon, 13 Jun 2005 09:50:29 -0400 [thread overview]
Message-ID: <20050613135029.GC8810@hmsendeavour.rdu.redhat.com> (raw)
In-Reply-To: <1118670162.13250.25.camel@localhost.localdomain>
On Mon, Jun 13, 2005 at 02:42:43PM +0100, Alan Cox wrote:
> On Sul, 2005-06-12 at 19:10, Neil Horman wrote:
> > How about this? Its the same feature, with an added check in fcntl_dirnotify to
> > ensure that only processes with CAP_SYS_ADMIN set can tell processes preforming
>
> Once you are monitoring and sending signals I think its time to ask if
> the interface is in totally the wrong place. Would it not be better if
> it was part of the ptrace interface to the monitored process ?
>
You mean add the ability to monitor directories for changes to the ptrace
interface entirely?
Regards
Neil
--
/***************************************************
*Neil Horman
*Software Engineer
*Red Hat, Inc.
*nhorman@redhat.com
*gpg keyid: 1024D / 0x92A74FA1
*http://pgp.mit.edu
***************************************************/
next prev parent reply other threads:[~2005-06-13 13:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 0:05 Neil Horman
2005-06-11 18:07 ` Matthew Wilcox
2005-06-11 19:35 ` Neil Horman
2005-06-12 18:10 ` Neil Horman
2005-06-13 6:13 ` Arjan van de Ven
2005-06-13 13:48 ` Neil Horman
2005-06-13 14:03 ` Alan Cox
2005-06-13 15:12 ` Neil Horman
2005-06-13 13:42 ` Alan Cox
2005-06-13 13:50 ` Neil Horman [this message]
2005-06-13 15:10 ` Alan Cox
2005-06-13 15:22 ` Matthew Wilcox
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=20050613135029.GC8810@hmsendeavour.rdu.redhat.com \
--to=nhorman@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
/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®