From: Andrew Morton <akpm@linux-foundation.org>
To: Philippe De Muyter <phdm@macqel.be>
Cc: linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] init/do_mounts.c: treat EROFS like EACCES
Date: Thu, 19 Jun 2014 14:19:50 -0700 [thread overview]
Message-ID: <20140619141950.18b9026d7d06694291eea311@linux-foundation.org> (raw)
In-Reply-To: <1403107964-1082-1-git-send-email-phdm@macqel.be>
On Wed, 18 Jun 2014 18:12:44 +0200 Philippe De Muyter <phdm@macqel.be> wrote:
> some combinations of filesystem and block device (at least vfat on mmc)
> yield -EROFS instead of -EACCES when the device is read-only. Retry
> mounting with MS_RDONLY set, just like for the EACCES case, instead of
> failing directly.
>
> ...
>
> --- a/init/do_mounts.c
> +++ b/init/do_mounts.c
> @@ -394,6 +394,7 @@ retry:
> case 0:
> goto out;
> case -EACCES:
> + case -EROFS:
> flags |= MS_RDONLY;
> goto retry;
> case -EINVAL:
hm, what's going on here. I'd have thought it to be very logical that
file_system_type.mount() would return EROFS if the device is read-only!
But I'm suspecting that there is some convention that the fs is
supposed to return EACCES in this case. So *perhaps* it is vfat-on-mmc
which needs fixing. Dunno.
Al, are you able to shed light?
next prev parent reply other threads:[~2014-06-19 21:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 16:12 Philippe De Muyter
2014-06-19 21:19 ` Andrew Morton [this message]
2014-06-19 23:09 ` Dave Chinner
2014-06-20 8:39 ` [PATCH] VFS: mount must return EACCES, not EROFS Philippe De Muyter
2014-06-27 8:20 ` [PATCH PING] " Philippe De Muyter
2014-07-02 19:46 ` Andrew Morton
2014-07-03 16:29 ` Philippe De Muyter
2014-07-08 21:02 ` Andrew Morton
2014-07-15 10:05 ` Philippe De Muyter
2014-06-20 13:13 ` [PATCH] init/do_mounts.c: treat EROFS like EACCES Philippe De Muyter
2014-06-23 9:22 ` Karel Zak
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=20140619141950.18b9026d7d06694291eea311@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phdm@macqel.be \
--cc=viro@zeniv.linux.org.uk \
/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®