[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YmD2R0AJ54yPRZhR@infradead.org>
Date: Wed, 20 Apr 2022 23:14:31 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Logan Gunthorpe <logang@...tatee.com>
Cc: linux-kernel@...r.kernel.org, linux-raid@...r.kernel.org,
Song Liu <song@...nel.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 v2 05/12] md/raid5: Factor out helper from
raid5_make_request() loop
> + if (unlikely(conf->reshape_progress != MaxSector)) {
> + /* spinlock is needed as reshape_progress may be
Normal kernel style is to stat with a
/*
line and to captalize the first word. (also applies for a few other
comments).
> + if (must_retry) {
> + raid5_release_stripe(sh);
> + return STRIPE_SCHEDULE_AND_RETRY;
The raid5_release_stripe cleanup is duplicated a few times. I think
using goto based unwinding would be hepful in this function.
Powered by blists - more mailing lists