From: Olivier Galibert <galibert@pobox.com>
To: Tigran Aivazian <tigran@veritas.com>
Cc: Alexander Viro <viro@math.psu.edu>,
Hugh Dickins <hugh@veritas.com>,
Andries Brouwer <aeb@veritas.com>,
linux-kernel@vger.kernel.org
Subject: Re: access() says EROFS even for device files if /dev is mounted RO
Date: Fri, 1 Dec 2000 12:12:48 -0500 [thread overview]
Message-ID: <20001201121248.A13401@zalem.puupuu.org> (raw)
In-Reply-To: <Pine.GSO.4.21.0011291051010.14112-100000@weyl.math.psu.edu> <Pine.LNX.4.21.0011291636440.1306-100000@penguin.homenet>
In-Reply-To: <Pine.LNX.4.21.0011291636440.1306-100000@penguin.homenet>; from tigran@veritas.com on Wed, Nov 29, 2000 at 04:40:29PM +0000
On Wed, Nov 29, 2000 at 04:40:29PM +0000, Tigran Aivazian wrote:
> b) what should be the return of access(W_OK) (or, the same, open() for
> write with switched uid) for devices on a readonly-mounted filesystems?
>
> Should the majority win? I.e. should we say OK, as we do now?
My gut feeling on this is that when you mount a filesystem readonly
you mean "I don't want the filesystem to be modifiable". Opening a
device for write never modifies the filesystem directly. Devices are
gateways to resources external to the filesystem, the write permission
means something different for them.
Same is for sockets/pipes btw.
And I really wonder how you plan to fsck / if it has been uncleanly
unmounted and includes /dev.
OG.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-01 17:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-27 3:35 Peter Cordes
2000-11-27 12:42 ` Andries Brouwer
2000-11-27 21:47 ` Rogier Wolff
2000-11-28 0:09 ` Andries Brouwer
2000-11-28 14:04 ` Rogier Wolff
2000-11-28 21:37 ` Andries Brouwer
2000-11-29 12:01 ` Hugh Dickins
2000-11-29 12:39 ` Alexander Viro
2000-11-29 15:46 ` Hugh Dickins
2000-11-29 16:18 ` Alexander Viro
2000-11-29 16:40 ` Tigran Aivazian
2000-11-29 16:52 ` Alexander Viro
2000-12-01 17:12 ` Olivier Galibert [this message]
2000-12-01 17:59 ` Richard B. Johnson
2000-11-29 16:24 ` Tigran Aivazian
2000-11-29 16:25 ` Tigran Aivazian
2000-11-29 16:42 ` Alexander Viro
2000-11-29 16:58 ` Tigran Aivazian
2000-11-29 17:07 ` Tigran Aivazian
2000-11-29 16:48 ` Hugh Dickins
2000-11-29 14:24 ` Richard B. Johnson
2000-11-29 14:33 ` Broken NTFS Joseph K. Malek
2000-11-29 19:28 ` Jeff V. Merkey
2000-11-28 22:56 ` access() says EROFS even for device files if /dev is mounted RO Peter Cordes
2000-11-28 23:23 ` Alexander Viro
2000-11-29 17:17 Andries.Brouwer
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=20001201121248.A13401@zalem.puupuu.org \
--to=galibert@pobox.com \
--cc=aeb@veritas.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.com \
--cc=viro@math.psu.edu \
/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®