linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: Shaohua Li <shli@kernel.org>
Cc: Linux-RAID <linux-raid@vger.kernel.org>,
	Nanda Kishore Chinnaram <Nanda_Kishore_Chinna@dell.com>
Subject: Re: [md PATCH] md: handle read-only member devices better.
Date: Sat, 15 Apr 2017 14:45:31 +1000	[thread overview]
Message-ID: <877f2muvmc.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20170413054723.2spvhtze6bljkaop@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 2046 bytes --]

On Wed, Apr 12 2017, Shaohua Li wrote:

> On Thu, Apr 13, 2017 at 08:53:48AM +1000, Neil Brown wrote:
>> 
>> 1/ If an array has any read-only devices when it is started,
>>    the array itself must be read-only
>> 2/ A read-only device cannot be added to an array after it is
>>    started.
>> 3/ Setting an array to read-write should not succeed
>>    if any member devices are read-only
>
> Didn't get these. We call md_import_device() first to open under layer disk. We
> always use FMOD_READ|FMOD_WRITE to open the disk. So if the disk is ro,
> md_import_device should fail, we don't add the disk to the array. Why would we
> have such issues?
>

Because life isn't always as simple as we might like it to be. :-(

md_import_device() calls lock_rdev() which calls blkdev_get_by_dev().

blkdev_get_by_dev() doesn't pay much attention to the mode, nor does
blkdev_get() which it calls.  The main place where FMODE_WRITE could be
rejected on a read-only device is in the device's 'open()' function.  A
few open functions do check for read-only, but it isn't at all
consistent.
scsi/sd.c does, block/loop.c doesn't, nor does nvme.  Most drivers seem
to ignore the mode.

blkdev_get_by_path() has

	if ((mode & FMODE_WRITE) && bdev_read_only(bdev)) {
		blkdev_put(bdev, mode);
		return ERR_PTR(-EACCES);
	}

so when you open a device by path name you always get this check, but
not when you open a device by device-number like md does.
It is worth having a look at
Commit: e51900f7d38c ("block: revert block_dev read-only check")
from 2011.  The bdev_read_only() check was in blkdev_get() for a while,
but it was moved out because doing that broke md and dm and others.

So at present, callers of blkdev_get_by_dev() need to do their own
bdev_read_only() tests before writing.
We could discuss where in md.c is the best place to put them, but unless
you want to take on a largish project to 'fix' (or audit) all callers of
blkdev_get_by_dev(), they need to go in md somewhere.

Thanks,
NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-04-15  4:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 22:53 [md PATCH] md: handle read-only member devices better NeilBrown
2017-04-13  5:47 ` Shaohua Li
2017-04-15  4:45   ` NeilBrown [this message]
2017-04-15 20:22     ` Anthony Youngman
2017-04-17 23:31       ` NeilBrown
2017-04-20 20:24     ` Shaohua Li
2017-04-20 21:54       ` NeilBrown

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=877f2muvmc.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=Nanda_Kishore_Chinna@dell.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=shli@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;
as well as URLs for NNTP newsgroup(s).