mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Neil Horman <nhorman@redhat.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	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 15:03:32 +0100	[thread overview]
Message-ID: <1118671411.13260.31.camel@localhost.localdomain> (raw)
In-Reply-To: <20050613134826.GB8810@hmsendeavour.rdu.redhat.com>

On Llu, 2005-06-13 at 14:48, Neil Horman wrote:
> The idea I had was to catch processes which are preforming ostensibly
> undesireable filesystem operations (as defined by the actions that F_NOTIFY can
> monitor).  I'm not sure how else to avoid the race condition that can arise
> between the delivery of the F_NOTIFY signal to the monitoring process, and the
> exiting of the monitored process. If you have another thought, I'm certainly
> open to it.

I'm more worried you will make things worse not better. My first thought
was what stops me just filling up the file table with admin work
possibly also involving setuid processes so the end user cannot rescue
the situation.

If its trying to do debugging then ptrace makes sense and the parent
would be notified. Ptrace deals with exit of tracer and security for
you. If you are trying to implement a security policy then the selinux
hooks already allow you to block access to those files by selected
processes anyway just as your F_NOTIFY hook would do, and you could even
write a new security layer with a daemon that decided for the F_NOTIFY
equivalents.

Alan


  reply	other threads:[~2005-06-13 14: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
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 [this message]
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=1118671411.13260.31.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=arjan@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --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®