From: Pavel Machek <pavel@suse.cz>
To: Alexander Viro <viro@math.psu.edu>
Cc: Bryan Henderson <hbryan@us.ibm.com>,
linux-fsdevel@vger.kernel.org,
linux-fsdevel-owner@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jean-Marc Saffroy <saffroy@ri.silicomp.fr>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [RFD] readonly/read-write semantics
Date: Tue, 4 Sep 2001 16:58:37 +0000 [thread overview]
Message-ID: <20010904165836.A48@toy.ucw.cz> (raw)
In-Reply-To: <OF8E62B3C8.CD1E8E23-ON87256AB9.007E8B1A@boulder.ibm.com> <Pine.GSO.4.21.0109010015380.15931-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0109010015380.15931-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Sat, Sep 01, 2001 at 12:23:05AM -0400
Hi!
> > 2) I'd like to see a readonly mount state defined as "the filesystem will
> > not change. Period." Not for system calls in progress, not for cache
> > synchronization, not to set an "unmounted" flag, not for writes that are
> > queued in the device driver or device. (That last one may stretch
> > feasability, but it's a worthy goal anyway).
>
> It doesn't work. Think of r/o mounting of remote filesystem. Do you
> suggest that it should make it impossible to change from other clients?
Okay, make the definition
"this kernel will not attempt to change anything on that filesystem".
This does not neccesarily mean -oro should have this semantics, maybe we
need something like -orealro, but we should have some mode when writing on
that disk is taboo. [I need that for suspend-to-disk support: I need to
write suspend data do disk, while I need noone to touch those disks,
because I already took snapshot.]
Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
next prev parent reply other threads:[~2001-09-04 18:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-31 23:35 Bryan Henderson
2001-09-01 4:23 ` Alexander Viro
2001-09-01 14:42 ` Ingo Oeser
2001-09-01 16:44 ` Alexander Viro
2001-09-01 17:13 ` Nicholas Knight
2001-09-04 2:07 ` Jean-Marc Saffroy
2001-09-04 4:09 ` Alexander Viro
2001-09-04 9:26 ` Xavier Bestel
2001-09-04 10:15 ` Alexander Viro
2001-09-04 10:20 ` Xavier Bestel
2001-09-04 10:28 ` Alexander Viro
2001-09-04 10:59 ` Xavier Bestel
2001-09-04 11:29 ` Alexander Viro
2001-09-04 17:03 ` Pavel Machek
2001-09-04 16:58 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-05 2:34 Bryan Henderson
2001-09-04 19:50 Bryan Henderson
2001-09-05 2:15 ` Alexander Viro
2001-09-04 18:39 Bryan Henderson
2001-09-01 0:38 Bryan Henderson
2001-08-31 17:18 [Q] [VFS] NULL f_dentry for opened files ; possible race condition Jean-Marc Saffroy
2001-08-31 20:56 ` [RFD] readonly/read-write semantics Alexander Viro
2001-09-01 13:08 ` Juan Quintela
2001-09-04 1:16 ` Jean-Marc Saffroy
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=20010904165836.A48@toy.ucw.cz \
--to=pavel@suse.cz \
--cc=hbryan@us.ibm.com \
--cc=linux-fsdevel-owner@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saffroy@ri.silicomp.fr \
--cc=torvalds@transmeta.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®