From: Guoqing Jiang Date: Wed, 17 Aug 2022 12:05:14 +0000 (+0800) Subject: md: call __md_stop_writes in md_stop X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=1678ca35b80a94d474fdc31e2497ce5d7ed52512;p=GitHub%2FLineageOS%2Fandroid_kernel_motorola_exynos9610.git md: call __md_stop_writes in md_stop commit 0dd84b319352bb8ba64752d4e45396d8b13e6018 upstream. From the link [1], we can see raid1d was running even after the path raid_dtr -> md_stop -> __md_stop. Let's stop write first in destructor to align with normal md-raid to fix the KASAN issue. [1]. https://lore.kernel.org/linux-raid/CAPhsuW5gc4AakdGNdF8ubpezAuDLFOYUO_sfMZcec6hQFm8nhg@mail.gmail.com/T/#m7f12bf90481c02c6d2da68c64aeed4779b7df74a Fixes: 48df498daf62 ("md: move bitmap_destroy to the beginning of __md_stop") Reported-by: Mikulas Patocka Signed-off-by: Guoqing Jiang Signed-off-by: Song Liu Signed-off-by: Greg Kroah-Hartman --- diff --git a/drivers/md/md.c b/drivers/md/md.c index 36d4cc1d7429..72f64ec88602 100644 --- a/drivers/md/md.c +++ b/drivers/md/md.c @@ -5908,6 +5908,7 @@ void md_stop(struct mddev *mddev) /* stop the array and free an attached data structures. * This is called from dm-raid */ + __md_stop_writes(mddev); __md_stop(mddev); if (mddev->bio_set) bioset_free(mddev->bio_set);