From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932185AbbLGO0Y (ORCPT ); Mon, 7 Dec 2015 09:26:24 -0500 Received: from mail-yk0-f179.google.com ([209.85.160.179]:35018 "EHLO mail-yk0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754735AbbLGO0X (ORCPT ); Mon, 7 Dec 2015 09:26:23 -0500 Date: Mon, 7 Dec 2015 09:26:21 -0500 From: Tejun Heo To: Andrey Ryabinin Cc: Wu Fengguang , Andrew Morton , linux-mm@kvack.org, LKML , Dmitry Vyukov , Sasha Levin Subject: Re: undefined shift in wb_update_dirty_ratelimit() Message-ID: <20151207142621.GA7012@mtj.duckdns.org> References: <566594E2.3050306@odin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <566594E2.3050306@odin.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, Andrey. On Mon, Dec 07, 2015 at 05:17:06PM +0300, Andrey Ryabinin wrote: > I've hit undefined shift in wb_update_dirty_ratelimit() which does some > mysterious 'step' calculations: > > /* > * Don't pursue 100% rate matching. It's impossible since the balanced > * rate itself is constantly fluctuating. So decrease the track speed > * when it gets close to the target. Helps eliminate pointless tremors. > */ > step >>= dirty_ratelimit / (2 * step + 1); > > > dirty_ratelimit = INIT_BW and step = 0 results in this: > > [ 5006.957366] ================================================================================ > [ 5006.957798] UBSAN: Undefined behaviour in ../mm/page-writeback.c:1286:7 > [ 5006.958091] shift exponent 25600 is too large for 64-bit type 'long unsigned int' We prolly should do sth like shift = dirty_ratelimit / (2 * step = 1); if (shift < BITS_PER_LONG) { step = (step >> shift) + 7 / 8; } else { step = 0; } Thanks. -- tejun