From: David Howells <dhowells@redhat.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: dhowells@redhat.com, hch@infradead.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, viro@ZenIV.linux.org.uk,
adilger@sun.com, alan@lxorguk.ukuu.org.uk,
akpm@linux-foundation.org
Subject: Re: [RFC] O_NOACC: open without any access
Date: Tue, 23 Jun 2009 16:52:17 +0100 [thread overview]
Message-ID: <16370.1245772337@redhat.com> (raw)
In-Reply-To: <E1MJ7gC-0007mx-CY@pomaz-ex.szeredi.hu>
Miklos Szeredi <miklos@szeredi.hu> wrote:
> Right, but that makes it useless for things which want to open it
> despite having no permission on the file.
For my purposes, if I'm going to emulate pioctl() in userspace, I also need to
be able to open device files that don't have drivers available, and when you
do open a dev file in this manner, it must _not_ call the ->open() routine of
the device driver.
David
next prev parent reply other threads:[~2009-06-23 15:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 6:55 [RFC] O_NOACC: open without any access Miklos Szeredi
2009-06-23 13:46 ` Christoph Hellwig
2009-06-23 14:12 ` Miklos Szeredi
2009-06-23 14:34 ` Christoph Hellwig
2009-06-23 15:13 ` Miklos Szeredi
2009-06-23 15:52 ` David Howells [this message]
2009-06-23 16:06 ` Alan Cox
2009-06-23 16:10 ` David Howells
2009-06-23 16:31 ` Miklos Szeredi
2009-06-23 17:05 ` David Howells
2009-06-23 17:34 ` Linus Torvalds
2009-06-23 20:04 ` Miklos Szeredi
2009-06-23 22:44 ` David Howells
2009-06-24 10:53 ` Al Viro
2009-06-24 11:12 ` Miklos Szeredi
2009-06-24 16:40 ` Linus Torvalds
2009-06-23 16:33 ` Alan Cox
2009-06-23 17:20 ` David Howells
2009-06-23 16:53 ` Christoph Hellwig
2009-06-23 16:59 ` David Howells
2009-06-24 17:02 ` Ulrich Drepper
2009-06-24 17:02 ` Ulrich Drepper
2009-06-24 18:06 ` Miklos Szeredi
2009-06-24 18:06 ` Miklos Szeredi
2009-06-24 18:34 ` Ulrich Drepper
2009-06-24 18:34 ` Ulrich Drepper
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=16370.1245772337@redhat.com \
--to=dhowells@redhat.com \
--cc=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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.