[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=whzdxBuoeTP1uJrxRQYtwOxPDYuP92c8e=_K5T1xHy7Ug@mail.gmail.com>
Date: Mon, 3 Jan 2022 11:53:18 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Norbert Warmuth <nwarmuth@...nline.de>,
Jens Axboe <axboe@...nel.dk>
Cc: Guoqing Jiang <guoqing.jiang@...ux.dev>,
Song Liu <songliubraving@...com>, linux-raid@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [Regression] md/raid1: write-intent logging/bitmap issue since
fd3b6975e9c1 - v5.16-rc1
[ Jens wasn't cc'd for some reason but was the signer-off-on the patch
you bisected to. Added him to the cc. I'll bounce the original
separately, as I also don't see this on lore.kernel.org - it might not
have gotten there yet ]
On Mon, Jan 3, 2022 at 11:30 AM Norbert Warmuth <nwarmuth@...nline.de> wrote:
>
> Please verify and either revert or fixup fd3b6975e9c1 if my analysis is
> correct.
Can you check if moving the WriteMostly bit to the "do behind I/O?"
section fixes things for you?
IOW, something like the attached patch..
Warning: This is very much a "Money see, monkey do" patch. I'm not
really familiar with the raid1 code ]
But yeah, if you see corruption and there isn't an absolutely trivial
fix for this, we should revert.
Linus
View attachment "patch.diff" of type "text/x-patch" (816 bytes)
Powered by blists - more mailing lists