Btw, what's the best way to get any response to this series?
But this and the predecessor seem to have completly fallen on deaf
ears.
--
To unsubscribe from this list: send the line "unsubscribe linux-block" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.k
bdev->bd_contains is not stable before calling __blkdev_get().
When __blkdev_get() is called on a parition with ->bd_openers == 0
it sets
bdev->bd_contains = bdev;
which is not correct for a partition.
After a call to __blkdev_get() succeeds, ->bd_openers will be > 0
and then ->bd_contains is st
Allow per-device "failfast" flag to be set when creating an
array or adding devices to an array.
When re-adding a device which had the failfast flag, it can be removed
using --nofailfast.
failfast status is printed in --detail and --examine output.
Signed-off-by: NeilBrown
---
Hi Jes,
this p
Hi Neil,
2016-11-24 5:47 GMT+01:00 NeilBrown :
> On Sat, Nov 19 2016, Jack Wang wrote:
>
>> 2016-11-18 6:16 GMT+01:00 NeilBrown :
>>> Hi,
>>>
>>> I've been sitting on these patches for a while because although they
>>> solve a real problem, it is a fairly limited use-case, and I don't
>>> reall
The goto is correct. "rc" is already set to -EBUSY so there is no need
to do anything with that.
Signed-off-by: Dan Carpenter
diff --git a/drivers/block/swim3.c b/drivers/block/swim3.c
index c264f2d..59b4a41 100644
--- a/drivers/block/swim3.c
+++ b/drivers/block/swim3.c
@@ -1179,7 +1179,6 @@ st
