From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: "Илья Тумайкин" <librarian_rus@yahoo.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: A regression in recent 3.2 kernel: bdi_dirty_limit() divide error
Date: Sat, 07 Jan 2012 17:35:25 +0100 [thread overview]
Message-ID: <1325954125.2442.27.camel@twins> (raw)
In-Reply-To: <20120107145645.GA4997@localhost>
On Sat, 2012-01-07 at 22:56 +0800, Wu Fengguang wrote:
> Subject:
> Date: Sat Jan 07 22:50:45 CST 2012
>
> The uninitilized shift may lead to denominator=0 in
> prop_fraction_percpu() and divide error in bdi_dirty_limit().
I'm not seeing how, only proc_change_shift() can change ->index, and it
does that after it writes ->pg[index]->shift.
> Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
> ---
> lib/proportions.c | 1 +
> 1 file changed, 1 insertion(+)
>
> --- linux.orig/lib/proportions.c 2012-01-07 22:50:29.000000000 +0800
> +++ linux/lib/proportions.c 2012-01-07 22:50:37.000000000 +0800
> @@ -82,6 +82,7 @@ int prop_descriptor_init(struct prop_des
>
> pd->index = 0;
> pd->pg[0].shift = shift;
> + pd->pg[1].shift = shift;
> mutex_init(&pd->mutex);
> err = percpu_counter_init(&pd->pg[0].events, 0);
> if (err)
>
>
next prev parent reply other threads:[~2012-01-07 16:35 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 [this message]
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
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=1325954125.2442.27.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=fengguang.wu@intel.com \
--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).