[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Ypmt+AGg76+lTeko@infradead.org>
Date: Thu, 2 Jun 2022 23:45:12 -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>,
Donald Buczek <buczek@...gen.mpg.de>,
Guoqing Jiang <guoqing.jiang@...ux.dev>,
Xiao Ni <xni@...hat.com>, Stephen Bates <sbates@...thlin.com>,
Martin Oliveira <Martin.Oliveira@...eticom.com>,
David Sloan <David.Sloan@...eticom.com>
Subject: Re: [PATCH v3 11/11] md/raid5-ppl: Fix argument order in
bio_alloc_bioset()
On Thu, Jun 02, 2022 at 12:18:17PM -0600, Logan Gunthorpe wrote:
> bio_alloc_bioset() takes a block device, number of vectors, the
> OP flags, the GFP mask and the bio set. However when the prototype
> was changed, the callisite in ppl_do_flush() had the OP flags and
> the GFP flags reversed. This introduced some sparse error:
>
> drivers/md/raid5-ppl.c:632:57: warning: incorrect type in argument 3
> (different base types)
> drivers/md/raid5-ppl.c:632:57: expected unsigned int opf
> drivers/md/raid5-ppl.c:632:57: got restricted gfp_t [usertype]
> drivers/md/raid5-ppl.c:633:61: warning: incorrect type in argument 4
> (different base types)
> drivers/md/raid5-ppl.c:633:61: expected restricted gfp_t [usertype]
> gfp_mask
> drivers/md/raid5-ppl.c:633:61: got unsigned long long
>
> The sparse error introduction may not have been reported correctly by
> 0day due to other work that was cleaning up other sparse errors in this
> area.
>
> Fixes: 609be1066731 ("block: pass a block_device and opf to bio_alloc_bioset")
> Signed-off-by: Logan Gunthorpe <logang@...tatee.com>
Ooops. Looks good:
Reviewed-by: Christoph Hellwig <hch@....de>
(and should probably be first in the series)
Powered by blists - more mailing lists