diff options
| author | Guoqing Jiang <[email protected]> | 2022-08-17 12:05:14 +0000 |
|---|---|---|
| committer | Song Liu <[email protected]> | 2022-08-24 18:19:59 +0000 |
| commit | 0dd84b319352bb8ba64752d4e45396d8b13e6018 (patch) | |
| tree | 1923aaa23f15ff5733d753813bf7d5bb60e3fd32 /drivers/usb/cdns3/cdns3-imx.c | |
| parent | Revert "md-raid: destroy the bitmap after destroying the thread" (diff) | |
| download | kernel-0dd84b319352bb8ba64752d4e45396d8b13e6018.tar.gz kernel-0dd84b319352bb8ba64752d4e45396d8b13e6018.zip | |
md: call __md_stop_writes in md_stop
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 <[email protected]>
Signed-off-by: Guoqing Jiang <[email protected]>
Signed-off-by: Song Liu <[email protected]>
Diffstat (limited to 'drivers/usb/cdns3/cdns3-imx.c')
0 files changed, 0 insertions, 0 deletions