From: "David M. Lloyd" <dmlloyd@flurg.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ulrich Drepper <drepper@redhat.com>, Ingo Molnar <mingo@elte.hu>,
Jeff Garzik <jeff@garzik.org>, Zach Brown <zach.brown@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arjan van de Ven <arjan@infradead.org>,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@zip.com.au>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
"David S. Miller" <davem@davemloft.net>,
Suparna Bhattacharya <suparna@in.ibm.com>,
Jens Axboe <jens.axboe@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Syslets, Threadlets, generic AIO support, v6
Date: Wed, 30 May 2007 16:51:51 -0500 [thread overview]
Message-ID: <20070530165151.6c2719eb@localhost> (raw)
In-Reply-To: <alpine.LFD.0.98.0705301422230.26602@woody.linux-foundation.org>
On Wed, 30 May 2007 14:27:52 -0700 (PDT)
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> Well, don't think of it as a special case at all: think of bit 30 as
> a "the user asked for a non-linear fd".
If the sole point is to protect an fd from being closed or operated on
outside of a certain context, why not just provide the ability to
"protect" an fd to prevent its use. Maybe a pair of syscalls like
"fdprotect" and "fdunprotect" that take an fd and an integer key.
Protected fds would return EBADF or something if accessed. The same
integer key must be provided to fdunprotect in order to gain access
to it again. Then glibc or valgrind or whatever would just unprotect
the fd before operating on it.
- DML
next prev parent reply other threads:[~2007-05-30 22:20 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 21:27 Syslets, Threadlets, generic AIO support, v6 Zach Brown
2007-05-29 21:49 ` Linus Torvalds
2007-05-29 22:49 ` Zach Brown
2007-05-29 22:16 ` Jeff Garzik
2007-05-29 23:09 ` Zach Brown
2007-05-29 23:20 ` Ulrich Drepper
2007-05-30 1:11 ` Dave Jones
2007-05-30 17:08 ` Zach Brown
2007-05-30 7:26 ` Ingo Molnar
2007-05-30 7:20 ` Ingo Molnar
2007-05-30 7:31 ` Ulrich Drepper
2007-05-30 8:42 ` Ingo Molnar
2007-05-30 8:51 ` Evgeniy Polyakov
2007-05-30 9:05 ` Ingo Molnar
2007-05-30 15:16 ` Linus Torvalds
2007-05-30 15:39 ` Ulrich Drepper
2007-05-30 19:40 ` Davide Libenzi
2007-05-30 19:55 ` Ulrich Drepper
2007-05-30 20:00 ` Linus Torvalds
2007-05-30 20:21 ` Davide Libenzi
2007-05-30 20:31 ` Eric Dumazet
2007-05-30 20:44 ` Linus Torvalds
2007-05-30 21:53 ` Eric Dumazet
2007-05-30 21:31 ` Davide Libenzi
2007-05-30 21:16 ` Ulrich Drepper
2007-05-30 21:27 ` Linus Torvalds
2007-05-30 21:47 ` Ulrich Drepper
2007-05-30 22:06 ` Davide Libenzi
2007-05-30 21:48 ` Davide Libenzi
2007-05-30 22:01 ` Linus Torvalds
2007-05-31 6:13 ` Ingo Molnar
2007-05-31 7:35 ` Eric Dumazet
2007-05-31 9:26 ` Ingo Molnar
2007-05-31 9:02 ` Ingo Molnar
2007-05-31 10:41 ` Eric Dumazet
2007-05-31 10:50 ` Ingo Molnar
2007-05-31 9:32 ` Ingo Molnar
2007-05-31 9:34 ` Jens Axboe
2007-05-30 22:09 ` Eric Dumazet
2007-05-30 21:51 ` David M. Lloyd [this message]
2007-05-30 22:24 ` William Lee Irwin III
2007-05-30 21:38 ` Jeremy Fitzhardinge
2007-05-30 21:39 ` Davide Libenzi
2007-05-30 21:36 ` Jeremy Fitzhardinge
2007-05-30 21:44 ` Linus Torvalds
2007-05-30 21:48 ` Linus Torvalds
2007-05-30 21:54 ` Jeremy Fitzhardinge
2007-05-30 22:27 ` Matt Mackall
2007-05-30 22:38 ` William Lee Irwin III
2007-05-30 8:32 ` Evgeniy Polyakov
2007-05-30 8:54 ` Ingo Molnar
2007-05-30 9:30 ` Evgeniy Polyakov
2007-05-30 9:28 ` Jeff Garzik
2007-05-30 13:02 ` Ingo Molnar
2007-05-30 13:20 ` Ingo Molnar
2007-05-30 15:31 ` Linus Torvalds
2007-05-30 16:09 ` Ingo Molnar
2007-05-30 17:57 ` Jens Axboe
2007-05-30 19:05 ` Mark Lord
2007-05-30 19:10 ` Jens Axboe
2007-05-30 19:15 ` Linus Torvalds
2007-05-30 19:32 ` Jens Axboe
2007-05-30 20:07 ` Eric Dumazet
2007-05-30 20:31 ` Linus Torvalds
2007-05-30 20:46 ` Eric Dumazet
2007-05-30 19:52 ` Davide Libenzi
2007-05-30 7:40 ` Jens Axboe
2007-05-30 16:55 ` Zach Brown
2007-05-30 17:33 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2007-05-31 8:15 Albert Cahalan
2007-05-31 9:50 ` Ingo Molnar
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=20070530165151.6c2719eb@localhost \
--to=dmlloyd@flurg.com \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=davem@davemloft.net \
--cc=drepper@redhat.com \
--cc=hch@infradead.org \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.com \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suparna@in.ibm.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=zach.brown@oracle.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