From: Jon Masters <jonmasters@gmail.com>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: PATCH: fix-readonly-policy-use-and-floppy-ro-rw-status
Date: Sat, 5 Nov 2005 19:39:18 +0000 [thread overview]
Message-ID: <35fb2e590511051139n2964f51ct761b8d97de86580d@mail.gmail.com> (raw)
In-Reply-To: <20051105190130.GP7992@ftp.linux.org.uk>
On 11/5/05, Al Viro <viro@ftp.linux.org.uk> wrote:
> ->remount_fs() certainly can refuse to go r/w - you don't need anything
> new for that, just don't leave MS_RDONLY in *flags.
Sure.
> The real trouble starts when fs wants to go r/o on its own
Although the situation here is really the other way around -
filesystem is mounted readonly (at least in this case with floppies -
but there are probably others too) and wants to go rw. When asked, we
need to check that the media is able to do handle that transition.
Currently I've bodged floppy.c to store this in policy/readonly (which
is what got me looking at genhd last week) but really there should be
a better way - one where we do this once we get to do_remount_sb or
whatever. This seems to be missing functionality.
> e.g. when it sees an error bad enough to warrant that. And that, BTW, is very
> likely to require more than just one bit in ->policy - we want all IO on that device
> to fail until after we actually close it during umount. As it is, we can get anything,
> including block allocations (e.g. if we have a dirty mapping and it gets written to disk).
Ok. So what you're saying is that this is more complex than I'd
implied and you're right :-) But aside from that, you're the expert
and I'm willing to go be a patch monkey, so just tell me what you
think is worth trying...
Jon.
next prev parent reply other threads:[~2005-11-05 19:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-05 18:27 Jon Masters
2005-11-05 18:33 ` Andrew Morton
2005-11-05 18:40 ` Jon Masters
2005-11-05 18:44 ` Al Viro
2005-11-05 18:51 ` Jon Masters
2005-11-05 19:01 ` Al Viro
2005-11-05 19:39 ` Jon Masters [this message]
2005-11-05 18:42 ` Al Viro
2005-11-05 18:48 ` Jon Masters
2005-11-05 18:41 ` Jeff Garzik
2005-11-06 10:59 ` Jon Masters
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=35fb2e590511051139n2964f51ct761b8d97de86580d@mail.gmail.com \
--to=jonmasters@gmail.com \
--cc=akpm@osdl.org \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ftp.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 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®