[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPhsuW7Ao3hTCjB2QvZcyqFYixSs8WYhWZoCqE3azqsttqDp4A@mail.gmail.com>
Date: Wed, 27 Jul 2022 22:55:49 -0700
From: Song Liu <song@...nel.org>
To: Logan Gunthorpe <logang@...tatee.com>
Cc: open list <linux-kernel@...r.kernel.org>,
linux-raid <linux-raid@...r.kernel.org>,
Christoph Hellwig <hch@...radead.org>,
Guoqing Jiang <guoqing.jiang@...ux.dev>,
Stephen Bates <sbates@...thlin.com>,
Martin Oliveira <Martin.Oliveira@...eticom.com>,
David Sloan <David.Sloan@...eticom.com>
Subject: Re: [PATCH 0/5] Bug fix for recent batching change
On Wed, Jul 27, 2022 at 2:06 PM Logan Gunthorpe <logang@...tatee.com> wrote:
>
> Hey,
>
> We hit another bug on my recent batching patch. In this case the
> bug has never been hit with the current md/md-next branch but
> some other patches we were working on changed the timing such
> that we hit this bug. It is theoretically possible to hit in
> the md/md-next batch so this patchset contains a fix.
>
> The fix is the last commit. The first four commits are some
> basic refactoring that makes the final commit a bit easier.
>
> A git repo is here and is based on current md/md-next (7a6f9e9cf1):
>
> https://github.com/sbates130272/linux-p2pmem raid5_batch_quiesce
Applied to md-next. Thanks!
Song
Powered by blists - more mailing lists