[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YFTJHRfNANFIUgOD@dschatzberg-fedora-PC0Y6AEN.dhcp.thefacebook.com>
Date: Fri, 19 Mar 2021 11:54:05 -0400
From: Dan Schatzberg <schatzberg.dan@...il.com>
To: Colin King <colin.king@...onical.com>
Cc: Jens Axboe <axboe@...nel.dk>, linux-block@...r.kernel.org,
kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH][next] loop: Fix missing max_active argument in
alloc_workqueue call
On Thu, Mar 18, 2021 at 03:16:26PM +0000, Colin King wrote:
> From: Colin Ian King <colin.king@...onical.com>
>
> The 3rd argument to alloc_workqueue should be the max_active count,
> however currently it is the lo->lo_number that is intended for the
> loop%d number. Fix this by adding in the missing max_active count.
>
Thanks for catching this Colin. I'm fairly new to kernel development.
Is there some tool I could have run locally to catch this?
Powered by blists - more mailing lists