Re: Weirdness of "mount -o remount,rw" with write-protected floppy

On 10/29/05, Jon Masters <[email protected]> wrote:

> The /only/ way I can see to "fix" this is to do a pointless open on
> the block device and see if that returns EROFS before allowing a
> remount. But I don't know what other hassle that will cause - I'll
> make the hack, but someone (Al?) who knows the code will need to
> comment because this might completely fuck up a lock somewhere.

Or change the policy for the underlying gendisk in floppy.c according
to what we find when we do an floppy_open on the device. Which is what
I'm looking at as a workaround.

Jon.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Weirdness of "mount -o remount,rw" with write-protected floppy
    • From: Evgeny Stambulchik <[email protected]>
  • Re: Weirdness of "mount -o remount,rw" with write-protected floppy
    • From: Jon Masters <[email protected]>

• Prev by Date: Re: [PATCH] drivers/input/keyboard: convert to dynamic input_dev allocation
• Next by Date: Fwd: segmentation fault when accessing /proc/ioports
• Previous by thread: Re: Weirdness of "mount -o remount,rw" with write-protected floppy
• Next by thread: yet another c language cross-reference for linux
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]