From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Villemoes Subject: Re: [PATCH 2/2] lib/lcm.c: lcm(n,0)=lcm(0,n) is 0, not n Date: Mon, 30 Mar 2015 21:38:27 +0200 Message-ID: <87y4me8edo.fsf@rasmusvillemoes.dk> References: <1418158984-25546-1-git-send-email-linux@rasmusvillemoes.dk> <1418158984-25546-2-git-send-email-linux@rasmusvillemoes.dk> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: (Mike Snitzer's message of "Sat, 28 Mar 2015 22:44:28 -0400") Sender: linux-kernel-owner@vger.kernel.org To: Mike Snitzer Cc: Andrew Morton , "linux-kernel@vger.kernel.org" , "Martin K. Petersen" , device-mapper development , Jens Axboe List-Id: dm-devel.ids On Sun, Mar 29 2015, Mike Snitzer wrote: > On Tue, Dec 9, 2014 at 4:03 PM, Rasmus Villemoes > wrote: >> Return the mathematically correct answer when an argument is 0. >> >> Signed-off-by: Rasmus Villemoes > > This change is the source of 3.19 regression for stacking device > limits, via commit 69c953c ("lib/lcm.c: lcm(n,0)=lcm(0,n) is 0, not > n"). > > > Rasmus, mathematical purity of lcm() aside, it'd have been nice if you > looked at the lcm() callers to determine whether you'd be breaking > them. I'm sorry about this. I thought I did check the callers, but evidently not well enough. Rasmus