From: Matthew Wilcox <matthew@wil.cx>
To: Neil Horman <nhorman@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
matthew@wil.cx
Subject: Re: [Patch][RFC] fcntl: add ability to stop monitored processes
Date: Sat, 11 Jun 2005 19:07:15 +0100 [thread overview]
Message-ID: <20050611180715.GK24611@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20050611000548.GA6549@hmsendeavour.rdu.redhat.com>
On Fri, Jun 10, 2005 at 08:05:48PM -0400, Neil Horman wrote:
> Hey there!
> I've recently developed this patch in pursuit of an ability to trap
> proceses making modifcations to monitored directories, and I thought It would be
> a nice feature to add to the mainline kernel. It basically adds a flag to the
> F_NOTIFY fcntl which optionally sends a SIGSTOP to the process making the
> flagged modifications to the monitored directories, and passes the pid of the
> stopped process to the monitoring process. I've tested it, and it works quite
> well for me. Looking for comments/approvial/incorporation.
What stops me from setting a DN_STOPSND on /lib and preventing any new
tasks from starting up?
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2005-06-11 18:06 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 [this message]
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
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=20050611180715.GK24611@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@redhat.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
all inboxes | Powered by JetHome®