From: Kent Overstreet <kent.overstreet@gmail.com>
To: util-linux@vger.kernel.org
Subject: Bug with read only handling in mount
Date: Mon, 3 Oct 2016 23:41:32 -0800 [thread overview]
Message-ID: <20161004074132.gnjun7jwarp2kcgr@kmo-pixel> (raw)
sys-utils/mount.c, mk_exit_code()
If the mount syscall returns EACCESS, the code treats this as meaning that RW
access to the block device wasn't allowed - it switches to RO for all future
mount attempts.
This is incorrect though, because EACCESS could just mean that that particular
filesystem doesn't support RW: iso9600 returns EACCESS if you try to mount RW.
The end result is that if we're trying to mount by trying every filesystem type
(your libblkid doesn't know about your filesystem yet..), and the correct
filesystem was listed after iso9600 in /proc/filesystems, mount will always
mount RO (unless you specify the filesystem type with -t).
next reply other threads:[~2016-10-04 7:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 7:41 Kent Overstreet [this message]
2016-10-04 8:29 ` Bug with read only handling in mount Karel Zak
2016-10-04 9:18 ` Kent Overstreet
2016-10-04 10:02 ` Karel Zak
2016-10-04 10:10 ` Kent Overstreet
2016-10-04 10:33 ` Karel Zak
2016-10-04 10:49 ` Jan Kara
2016-10-04 11:24 ` 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=20161004074132.gnjun7jwarp2kcgr@kmo-pixel \
--to=kent.overstreet@gmail.com \
--cc=util-linux@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