mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Masters <jonmasters@gmail.com>
To: Rob Landley <rob@landley.net>
Cc: Evgeny Stambulchik <Evgeny.Stambulchik@weizmann.ac.il>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix floppy.c to store correct ro/rw status in underlying gendisk
Date: Tue, 1 Nov 2005 02:36:42 +0000	[thread overview]
Message-ID: <35fb2e590510311836j4c7fbdf2u77a72ebbfd53790c@mail.gmail.com> (raw)
In-Reply-To: <200510311717.21676.rob@landley.net>

On 10/31/05, Rob Landley <rob@landley.net> wrote:
> On Monday 31 October 2005 05:57, Evgeny Stambulchik wrote:
> > Jon Masters wrote:
> > > Let me know if this fixes it for you - should bomb out now if you try.
> > > The error isn't the cleanest (blame mount), but it does fail.
> >
> > This works fine, thanks! For what it worth, though, mount -o remount,rw
> > says remounting read-only yet still returns success. (Opposite to
> > busybox, which now says "Permission denied" - rather misleading, but at
> > least it fails).
>
> That sounds like the string translation of EPERM returned by libc's
> strerror().  (At busybox we're frugal bastards; we don't include text
> messages when we can get the C library to provide them for us. :)

Indeed. Reminds me that I should clean up and send a form parser I
wrote for busybox to handle multi-part mime form posts in its
webserver while I'm at it. That's something it could do with even if
it's being frugal.

> But yeah, we're sticklers for correct behavior, and only attempt to remount
> readonly if we get EACCES or EROFS, not _just_ because we attempted a
> read/write mount and it failed.  (And yes, I personally tested this corner
> case.  We haven't started on an automated regression test script for mount
> yet because running it would require root access, but it's on the todo list
> as we upgrade the test suite in our Copious Free Time...)

You looked at running this inside a qemu environment (scratchbox), huh?

Jon.

  reply	other threads:[~2005-11-01  2:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29 17:25 Jon Masters
     [not found] ` <35fb2e590510291035n297aa22cv303ae77baeb5c213@mail.gmail.com>
2005-10-31 11:57   ` Evgeny Stambulchik
2005-10-31 15:58     ` Jon Masters
2005-10-31 23:17     ` Rob Landley
2005-11-01  2:36       ` Jon Masters [this message]
2005-11-01  7:21         ` Rob Landley
2005-11-01 13:53       ` Evgeny Stambulchik
2005-11-01 17:32         ` Rob Landley

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=35fb2e590510311836j4c7fbdf2u77a72ebbfd53790c@mail.gmail.com \
    --to=jonmasters@gmail.com \
    --cc=Evgeny.Stambulchik@weizmann.ac.il \
    --cc=jonathan@jonmasters.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    /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®