Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751318AbbLHRKQ (ORCPT ); Tue, 8 Dec 2015 12:10:16 -0500 Received: from mx1.redhat.com ([209.132.183.28]:58766 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750879AbbLHRKO (ORCPT ); Tue, 8 Dec 2015 12:10:14 -0500 Date: Tue, 8 Dec 2015 12:10:13 -0500 From: Mike Snitzer To: Arnd Bergmann Cc: dm-devel@redhat.com, Neil Brown , linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org, Alasdair Kergon , Sami Tolvanen , linux-arm-kernel@lists.infradead.org Subject: Re: dm verity: use sector_div for division Message-ID: <20151208171013.GA4263@redhat.com> References: <2666833.eM84rj4CYY@wuerfel> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2666833.eM84rj4CYY@wuerfel> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1105 Lines: 24 On Tue, Dec 08 2015 at 10:42am -0500, Arnd Bergmann wrote: > The dm verity sec implementation uses do_div for dividing a sector_t, > which is slower than necessary when sector_t is a 32-bit type, and > we now get a warning for this case: > > include/asm-generic/div64.h:224:22: warning: passing argument 1 of '__div64_32' from incompatible pointer type [-Wincompatible-pointer-types] > drivers/md/dm-verity-fec.c:725:6: note: in expansion of macro 'do_div' > if (do_div(f->rounds, f->rsn)) > > This changes the code to use sector_div instead, which does the > right thing and avoids the warning. Thanks, I'll fold this in. (Btw, I did review this use of do_div(): but only to answer whether there was potential for a 64bit divide. I concluded do_div() was fine but didn't look to see the data type for f->rounds was actually sector_t.) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/