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: Thu, 27 Oct 2005 16:09:47 -0500 [thread overview]
Message-ID: <200510271609.47309.rob@landley.net> (raw)
In-Reply-To: <4360C0A7.4050708@weizmann.ac.il>
On Thursday 27 October 2005 06:57, Evgeny Stambulchik wrote:
> The bug is present in both 2.4 and 2.6, and is specific to floppy
> devices. Other RO media I tried (CDROM, RO-exported NFS) are partially
> OK, in the sense that a write attempt returns an error; however, "mount
> -o remount,rw" always returns success (this might be a bug in mount).
Busybox "mount" maintainer's ears perk up to see if this is relevant. (After
all, we have a separate implementation you can try to see if it's a tool
bug.)
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. :)
Rob
next prev parent reply other threads:[~2005-10-27 21:09 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 [this message]
2005-10-28 11:55 ` Evgeny Stambulchik
2005-10-28 12:26 ` Rob Landley
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=200510271609.47309.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