All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: neilb@suse.de
Cc: linux-raid@vger.kernel.org
Subject: [RFC PATCH 0/2] a couple of readonly handling fixups
Date: Thu, 08 Jan 2009 00:24:33 -0700	[thread overview]
Message-ID: <20090108072023.9577.3585.stgit@dwillia2-linux.ch.intel.com> (raw)

The BUG_ON(mddev->ro == 1) in md_write_start can be triggered under two
circumstances in recent kernels.  One was reported by Justin Maggard:

1) Create an md array with >= 1 disk
2) Start a task writing to the array ("dd if=/dev/zero of=/dev/md0
bs=1M count=10000 &" does the trick for me)
3) Force an improper reboot with reboot -fn

...the other was discovered while investigating this issue.

1) Set a raid5 readyonly with mdadm
2) Set the array writable with blockdev
3) Attempt to write to the array

---

Dan Williams (2):
      Revert "Restore force switch of md array to readonly at reboot time."
      md: set mddev readonly flag on blkdev BLKROSET ioctl

 drivers/md/md.c |   35 ++++++++++++++++++++++++++++++-----
 1 files changed, 30 insertions(+), 5 deletions(-)


             reply	other threads:[~2009-01-08  7:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08  7:24 Dan Williams [this message]
2009-01-08  7:24 ` [PATCH 1/2] md: set mddev readonly flag on blkdev BLKROSET ioctl Dan Williams
2009-01-08  7:24 ` [PATCH 2/2] Revert "Restore force switch of md array to readonly at reboot time." Dan Williams
2009-01-18 23:07 ` [RFC PATCH 0/2] a couple of readonly handling fixups Neil Brown
2010-05-11 18:06   ` Dan Williams
2010-05-11 22:33     ` Neil Brown

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=20090108072023.9577.3585.stgit@dwillia2-linux.ch.intel.com \
    --to=dan.j.williams@intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.