From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Michael Buesch <mbuesch@freenet.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Albert Cahalan <albert@users.sourceforge.net>,
Eric Lammerts <eric@lammerts.org>,
Marc Ballarin <Ballarin.Marc@gmx.de>, Greg KH <greg@kroah.com>
Subject: Re: [RFC, PATCH] sys_revoke(), just a try. (was: Re: dynamic /dev security hole?)
Date: Thu, 12 Aug 2004 20:51:19 +0100 [thread overview]
Message-ID: <1092340279.22362.6.camel@localhost.localdomain> (raw)
In-Reply-To: <200408121849.20227.mbuesch@freenet.de>
On Iau, 2004-08-12 at 17:49, Michael Buesch wrote:
> +static ssize_t revoke_read(struct file *filp,
> + char *buf,
> + size_t count,
> + loff_t *ppos)
> +{
> + return 0;
> +}
-EIO I think but I'm not sure I remember the BSD behaviour in full
> +static int filp_revoke(struct file *filp, struct inode *inode)
> +{
First problem here is that the handle might still be in use
for mmap, so you'd need to undo mmaps on it. A second is that
while you can ->flush() here you can't really close it until the
file usage count hits zero.
You are btw tackling a really really hard problem and its more likely
the way to do this is to add revoke() methods to drivers and do it at
the driver level - as the tty layer does with vhangup.
next prev parent reply other threads:[~2004-08-12 20:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-08 12:47 dynamic /dev security hole? Albert Cahalan
2004-08-08 15:58 ` Marc Ballarin
2004-08-08 15:04 ` Albert Cahalan
2004-08-08 20:42 ` Greg KH
2004-08-08 16:21 ` Greg KH
2004-08-08 21:43 ` Marc Ballarin
2004-08-08 22:07 ` Marc Ballarin
2004-08-09 4:40 ` Eric Lammerts
2004-08-09 13:30 ` Michael Buesch
2004-08-09 13:19 ` Albert Cahalan
2004-08-09 16:54 ` Michael Buesch
2004-08-09 17:04 ` Eric Lammerts
2004-08-09 17:14 ` Michael Buesch
2004-08-10 0:21 ` Greg KH
2004-08-11 17:12 ` [RFC, PATCH] sys_revoke(), just a try. (was: Re: dynamic /dev security hole?) Michael Buesch
2004-08-12 16:49 ` Michael Buesch
2004-08-12 19:51 ` Alan Cox [this message]
2004-08-12 19:39 ` Albert Cahalan
2004-08-13 12:39 ` Michael Buesch
2004-08-09 14:49 ` dynamic /dev security hole? Alan Cox
2004-08-09 16:17 ` Eric Lammerts
2004-08-09 15:33 ` Alan Cox
2004-08-09 16:47 ` Eric Lammerts
2004-08-09 17:54 ` Alan Cox
2004-08-10 0:21 ` Greg KH
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=1092340279.22362.6.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Ballarin.Marc@gmx.de \
--cc=albert@users.sourceforge.net \
--cc=eric@lammerts.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbuesch@freenet.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.