md read-only fixes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: axboe@xxxxxxxxx, song@xxxxxxxxxx
Subject: md read-only fixes
From: Christoph Hellwig <hch@xxxxxx>
Date: Mon, 1 Feb 2021 14:17:19 +0100
Cc: guoqing.jiang@xxxxxxxxxxxxxxx, linux-block@xxxxxxxxxxxxxxx, linux-raid@xxxxxxxxxxxxxxx

Hi all,

patch 1 fixes a regression in md in for-5.12/block, and patch 2
fixes a little inconsistency in the same area.

Follow-Ups:
- Re: md read-only fixes
  - From: Jens Axboe
- [PATCH 2/2] md: use rdev_read_only in restart_array
  - From: Christoph Hellwig
- [PATCH 1/2] md: check for NULL ->meta_bdev before calling bdev_read_only
  - From: Christoph Hellwig

Prev by Date: [PATCH 2/2] md: use rdev_read_only in restart_array
Next by Date: Re: One failed raid device can't umount automatically
Previous by thread: [PATCH] super1: fix Floating point exception
Next by thread: [PATCH 1/2] md: check for NULL ->meta_bdev before calling bdev_read_only
Index(es):
- Date
- Thread

[Index of Archives] [Linux RAID Wiki] [ATA RAID] [Linux SCSI Target Infrastructure] [Linux Block] [Linux IDE] [Linux SCSI] [Linux Hams] [Device Mapper] [Device Mapper Cryptographics] [Kernel] [Linux Admin] [Linux Net] [GFS] [RPM] [git] [Yosemite Forum]

Powered by Linux