From: Wu Fengguang <wfg@linux.intel.com>
To: "Илья Тумайкин" <librarian_rus@yahoo.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] lib: proportion: lower PROP_MAX_SHIFT to 32 on 64-bit kernel
Date: Tue, 10 Jan 2012 23:01:30 +0800 [thread overview]
Message-ID: <20120110150130.GA10036@localhost> (raw)
In-Reply-To: <20120110145455.GA8999@localhost>
Ilya, would you post your /proc/vmstat?
I wonder if your proportion shift value is really large enough (> 32)
to trigger bug in this way.
Thanks,
Fengguang
On Tue, Jan 10, 2012 at 10:54:55PM +0800, Wu Fengguang wrote:
> PROP_MAX_SHIFT should be set to <=32 on 64-bit box. This fixes two bugs
> in the below lines of bdi_dirty_limit():
>
> bdi_dirty *= numerator;
> do_div(bdi_dirty, denominator);
>
> 1) divide error: do_div() only uses the lower 32 bit of the denominator,
> which may trimmed to be 0 when PROP_MAX_SHIFT > 32.
>
> 2) overflow: (bdi_dirty * numerator) could easily overflow if numerator
> used up to 48 bits, leaving only 16 bits to bdi_dirty
>
> Tested-by: Ilya Tumaykin <librarian_rus@yahoo.com>
> Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
> ---
> include/linux/proportions.h | 4 ++++
> 1 file changed, 4 insertions(+)
>
> --- linux.orig/include/linux/proportions.h 2012-01-09 11:51:19.000000000 +0800
> +++ linux/include/linux/proportions.h 2012-01-09 11:53:47.000000000 +0800
> @@ -81,7 +81,11 @@ void prop_inc_percpu(struct prop_descrip
> * Limit the time part in order to ensure there are some bits left for the
> * cycle counter and fraction multiply.
> */
> +#if BITS_PER_LONG == 32
> #define PROP_MAX_SHIFT (3*BITS_PER_LONG/4)
> +#else
> +#define PROP_MAX_SHIFT (BITS_PER_LONG/2)
> +#endif
>
> #define PROP_FRAC_SHIFT (BITS_PER_LONG - PROP_MAX_SHIFT - 1)
> #define PROP_FRAC_BASE (1UL << PROP_FRAC_SHIFT)
prev parent reply other threads:[~2012-01-10 15:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1325884395.57034.YahooMailClassic@web161605.mail.bf1.yahoo.com>
2012-01-07 14:56 ` A regression in recent 3.2 kernel: bdi_dirty_limit() divide error Wu Fengguang
2012-01-07 16:35 ` Peter Zijlstra
2012-01-08 2:33 ` Wu Fengguang
2012-01-08 10:19 ` Peter Zijlstra
2012-01-09 4:04 ` Wu Fengguang
[not found] ` <1326205945.62365.YahooMailClassic@web161603.mail.bf1.yahoo.com>
2012-01-10 14:38 ` Wu Fengguang
2012-01-09 4:55 ` Wu Fengguang
2012-01-10 14:54 ` [PATCH] lib: proportion: lower PROP_MAX_SHIFT to 32 on 64-bit kernel Wu Fengguang
2012-01-10 15:01 ` Wu Fengguang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120110150130.GA10036@localhost \
--to=wfg@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=jack@suse.cz \
--cc=librarian_rus@yahoo.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).