From: Rob Landley <rob@landley.net>
To: Evgeny Stambulchik <Evgeny.Stambulchik@weizmann.ac.il>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Weirdness of "mount -o remount,rw" with write-protected floppy
Date: Fri, 28 Oct 2005 07:26:56 -0500 [thread overview]
Message-ID: <200510280726.56684.rob@landley.net> (raw)
In-Reply-To: <436211B0.1050509@weizmann.ac.il>
On Friday 28 October 2005 06:55, Evgeny Stambulchik wrote:
> Rob Landley wrote:
> > But no, this one's clearly a kernel error. If the kernel is giving write
> > errors against the device afterwards, than the kernel's internal state
> > toggled successfully, which is all the mount syscall was trying to do.
> > Mount is just reporting whether or not the syscall succeeded, not whether
> > or not it should have. :)
>
> OK, so there are actually two separate bugs, it seems: one that
> remounting a RO media in the RW mode succeeds (this "works" for any RO
> media, as far as I can tell) and the second (this one is specific to the
> floppy driver only) that a further write to such a falsely rw-remounted
> media doesn't return (in the user space) an error.
It looks like one bug to me. The initial mount figures out that it's read
only, and the actual writes fail correctly, but remount isn't checking for
read only (and thus isn't failing).
Rob
next prev parent reply other threads:[~2005-10-28 12:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 11:57 Weirdness of "mount -o remount,rw" with write-protected floppy Evgeny Stambulchik
2005-10-27 15:05 ` Jon Masters
2005-10-29 11:58 ` Jon Masters
2005-10-29 13:10 ` Jon Masters
2005-10-27 21:09 ` Rob Landley
2005-10-28 11:55 ` Evgeny Stambulchik
2005-10-28 12:26 ` Rob Landley [this message]
2005-10-28 13:15 ` Evgeny Stambulchik
2005-10-28 13:50 ` Rob Landley
2005-10-28 14:52 ` Evgeny Stambulchik
2005-10-29 1:29 ` Rob Landley
2005-10-29 11:06 ` Evgeny Stambulchik
2005-10-29 16:02 ` Jon Masters
2005-10-29 17:05 ` 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=200510280726.56684.rob@landley.net \
--to=rob@landley.net \
--cc=Evgeny.Stambulchik@weizmann.ac.il \
--cc=linux-kernel@vger.kernel.org \
/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