From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751417Ab2LSVr2 (ORCPT ); Wed, 19 Dec 2012 16:47:28 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:44287 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750843Ab2LSVrW (ORCPT ); Wed, 19 Dec 2012 16:47:22 -0500 Date: Wed, 19 Dec 2012 13:47:21 -0800 From: Andrew Morton To: Guenter Roeck Cc: linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org, Juergen Beisert , Jean Delvare Subject: Re: [PATCH v2] linux/kernel.h: Fix DIV_ROUND_CLOSEST with unsigned divisors Message-Id: <20121219134721.bbde212f.akpm@linux-foundation.org> In-Reply-To: <1355928015-26212-1-git-send-email-linux@roeck-us.net> References: <1355928015-26212-1-git-send-email-linux@roeck-us.net> X-Mailer: Sylpheed 3.0.2 (GTK+ 2.20.1; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 19 Dec 2012 06:40:15 -0800 Guenter Roeck wrote: > Commit 263a523 fixes a warning seen with W=1 due to change in > DIV_ROUND_CLOSEST. Unfortunately, the C compiler converts divide operations > with unsigned divisors to unsigned, even if the dividend is signed and > negative (for example, -10 / 5U = 858993457). The C standard says "If one > operand has unsigned int type, the other operand is converted to unsigned > int", so the compiler is not to blame. > As a result, DIV_ROUND_CLOSEST(0, 2U) and similar operations now return > bad values, since the automatic conversion of expressions such as "0 - 2U/2" > to unsigned was not taken into account. > > Fix by checking for the divisor variable type when deciding which operation > to perform. This fixes DIV_ROUND_CLOSEST(0, 2U), but still returns bad values > for negative dividends divided by unsigned divisors. Mark the latter case as > unsupported. The changelog didn't describe the end-user visible effects of the bug. Please always include this information. Because... The patch is applicable to 3.7.x. Should we backport it?