From: Rob Landley <rob@landley.net>
Organization: Boundaries Unlimited
To: Evgeny Stambulchik <Evgeny.Stambulchik@weizmann.ac.il>
Subject: Re: Weirdness of "mount -o remount,rw" with write-protected floppy
Date: Thu, 27 Oct 2005 16:09:47 -0500
User-Agent: KMail/1.8
Cc: linux-kernel@vger.kernel.org
References: <4360C0A7.4050708@weizmann.ac.il>
In-Reply-To: <4360C0A7.4050708@weizmann.ac.il>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200510271609.47309.rob@landley.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1079
Lines: 22

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/