From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marco Stornelli Subject: Re: [PATCH 2/3] writeback: fix incorrect return value type of bdi_dirty_limit Date: Sun, 19 Aug 2012 12:23:15 +0200 Message-ID: <5030BE93.50909@gmail.com> References: <1345283361-7802-1-git-send-email-linkinjeon@gmail.com> <20120819021757.GB16796@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Namjae Jeon , akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org To: Fengguang Wu Return-path: Received: from mail-we0-f174.google.com ([74.125.82.174]:60594 "EHLO mail-we0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751287Ab2HSK3l (ORCPT ); Sun, 19 Aug 2012 06:29:41 -0400 In-Reply-To: <20120819021757.GB16796@localhost> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Il 19/08/2012 04:17, Fengguang Wu ha scritto: > On Sat, Aug 18, 2012 at 05:49:21AM -0400, Namjae Jeon wrote: >> unsigned long bdi_dirty_limit(struct backing_dev_info *bdi, unsigned long dirty) >> >> Above function return type is unsigned long, but return value is >> kept in "u64 bdi_dirty". >> It can return incorrect value by type casting. > > I don't see how the cast can return wrong value. > The u64 is necessary for the intermediate calculations. > > Thanks, > Fengguang > We are sure u64 is 8byte long, but unsigned long is 4byte long on 32-bit machine, so if bdi_dirty can assume values bigger than 2^32 there is an implicit truncate of its value, isn't it? Marco