All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Dave Chinner <david@fromorbit.com>, Jan Kara <jack@suse.cz>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/6] writeback: avoid unnecessary calculation of bdi dirty thresholds
Date: Mon, 19 Jul 2010 21:14:00 -0700	[thread overview]
Message-ID: <20100719211400.c2bd5494.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100720033437.GE6087@localhost>

On Tue, 20 Jul 2010 11:34:37 +0800 Wu Fengguang <fengguang.wu@intel.com> wrote:

> On Tue, Jul 20, 2010 at 05:35:20AM +0800, Andrew Morton wrote:
> > On Sun, 11 Jul 2010 10:06:59 +0800
> > Wu Fengguang <fengguang.wu@intel.com> wrote:
> > 
> > > Split get_dirty_limits() into global_dirty_limits()+bdi_dirty_limit(),
> > > so that the latter can be avoided when under global dirty background
> > > threshold (which is the normal state for most systems).
> > > 
> > 
> > mm/page-writeback.c: In function 'balance_dirty_pages_ratelimited_nr':
> > mm/page-writeback.c:466: warning: 'dirty_exceeded' may be used uninitialized in this function
> > 
> > This was a real bug.
> 
> Thanks! But how do you catch this? There are no warnings in my compile test.

Basic `make allmodconfig'.  But I use a range of different compiler
versions.  Different versions of gcc detect different stuff.  This was 4.1.0
or 4.0.2, I forget which.



WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Dave Chinner <david@fromorbit.com>, Jan Kara <jack@suse.cz>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/6] writeback: avoid unnecessary calculation of bdi dirty thresholds
Date: Mon, 19 Jul 2010 21:14:00 -0700	[thread overview]
Message-ID: <20100719211400.c2bd5494.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100720033437.GE6087@localhost>

On Tue, 20 Jul 2010 11:34:37 +0800 Wu Fengguang <fengguang.wu@intel.com> wrote:

> On Tue, Jul 20, 2010 at 05:35:20AM +0800, Andrew Morton wrote:
> > On Sun, 11 Jul 2010 10:06:59 +0800
> > Wu Fengguang <fengguang.wu@intel.com> wrote:
> > 
> > > Split get_dirty_limits() into global_dirty_limits()+bdi_dirty_limit(),
> > > so that the latter can be avoided when under global dirty background
> > > threshold (which is the normal state for most systems).
> > > 
> > 
> > mm/page-writeback.c: In function 'balance_dirty_pages_ratelimited_nr':
> > mm/page-writeback.c:466: warning: 'dirty_exceeded' may be used uninitialized in this function
> > 
> > This was a real bug.
> 
> Thanks! But how do you catch this? There are no warnings in my compile test.

Basic `make allmodconfig'.  But I use a range of different compiler
versions.  Different versions of gcc detect different stuff.  This was 4.1.0
or 4.0.2, I forget which.


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-07-20  4:15 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-11  2:06 [PATCH 0/6] writeback cleanups and trivial fixes Wu Fengguang
2010-07-11  2:06 ` Wu Fengguang
2010-07-11  2:06 ` Wu Fengguang
2010-07-11  2:06 ` [PATCH 1/6] writeback: take account of NR_WRITEBACK_TEMP in balance_dirty_pages() Wu Fengguang
2010-07-11  2:06   ` Wu Fengguang
2010-07-12 21:52   ` Andrew Morton
2010-07-12 21:52     ` Andrew Morton
2010-07-12 21:52     ` Andrew Morton
2010-07-13  8:58     ` Miklos Szeredi
2010-07-13  8:58       ` Miklos Szeredi
2010-07-15 14:50       ` Wu Fengguang
2010-07-15 14:50         ` Wu Fengguang
2010-07-11  2:06 ` [PATCH 2/6] writeback: reduce calls to global_page_state " Wu Fengguang
2010-07-11  2:06   ` Wu Fengguang
2010-07-11  2:06   ` Wu Fengguang
2010-07-26 15:19   ` Jan Kara
2010-07-26 15:19     ` Jan Kara
2010-07-27  3:59     ` Wu Fengguang
2010-07-27  3:59       ` Wu Fengguang
2010-07-27  9:12       ` Jan Kara
2010-07-27  9:12         ` Jan Kara
2010-07-28  2:04         ` Wu Fengguang
2010-07-28  2:04           ` Wu Fengguang
2010-08-03 14:55   ` Peter Zijlstra
2010-08-03 14:55     ` Peter Zijlstra
2010-07-11  2:06 ` [PATCH 3/6] writeback: avoid unnecessary calculation of bdi dirty thresholds Wu Fengguang
2010-07-11  2:06   ` Wu Fengguang
2010-07-11  2:06   ` Wu Fengguang
2010-07-12 21:56   ` Andrew Morton
2010-07-12 21:56     ` Andrew Morton
2010-07-12 21:56     ` Andrew Morton
2010-07-15 14:55     ` Wu Fengguang
2010-07-15 14:55       ` Wu Fengguang
2010-07-19 21:35   ` Andrew Morton
2010-07-19 21:35     ` Andrew Morton
2010-07-19 21:35     ` Andrew Morton
2010-07-20  3:34     ` Wu Fengguang
2010-07-20  3:34       ` Wu Fengguang
2010-07-20  3:34       ` Wu Fengguang
2010-07-20  4:14       ` Andrew Morton [this message]
2010-07-20  4:14         ` Andrew Morton
2010-08-03 15:03   ` Peter Zijlstra
2010-08-03 15:03     ` Peter Zijlstra
2010-08-03 15:10     ` Wu Fengguang
2010-08-03 15:10       ` Wu Fengguang
2010-08-04 16:41     ` Wu Fengguang
2010-08-04 16:41       ` Wu Fengguang
2010-08-04 17:10       ` Peter Zijlstra
2010-08-04 17:10         ` Peter Zijlstra
2010-07-11  2:07 ` [PATCH 4/6] writeback: dont redirty tail an inode with dirty pages Wu Fengguang
2010-07-11  2:07   ` Wu Fengguang
2010-07-12  2:01   ` Dave Chinner
2010-07-12  2:01     ` Dave Chinner
2010-07-12 15:31     ` Wu Fengguang
2010-07-12 15:31       ` Wu Fengguang
2010-07-12 22:13       ` Andrew Morton
2010-07-12 22:13         ` Andrew Morton
2010-07-15 15:35         ` Wu Fengguang
2010-07-15 15:35           ` Wu Fengguang
2010-07-11  2:07 ` [PATCH 5/6] writeback: fix queue_io() ordering Wu Fengguang
2010-07-11  2:07   ` Wu Fengguang
2010-07-11  2:07   ` Wu Fengguang
2010-07-12 22:15   ` Andrew Morton
2010-07-12 22:15     ` Andrew Morton
2010-07-12 22:15     ` Andrew Morton
2010-07-11  2:07 ` [PATCH 6/6] writeback: merge for_kupdate and !for_kupdate cases Wu Fengguang
2010-07-11  2:07   ` Wu Fengguang
2010-07-12  2:08   ` Dave Chinner
2010-07-12  2:08     ` Dave Chinner
2010-07-12 15:52     ` Wu Fengguang
2010-07-12 15:52       ` Wu Fengguang
2010-07-12 22:06       ` Dave Chinner
2010-07-12 22:06         ` Dave Chinner
2010-07-12 22:22       ` Andrew Morton
2010-07-12 22:22         ` Andrew Morton
2010-08-05 16:01         ` Wu Fengguang
2010-08-05 16:01           ` Wu Fengguang
2010-07-11  2:44 ` [PATCH 0/6] writeback cleanups and trivial fixes Christoph Hellwig
2010-07-11  2:44   ` Christoph Hellwig
2010-07-11  2:50   ` Wu Fengguang
2010-07-11  2:50     ` 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=20100719211400.c2bd5494.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=david@fromorbit.com \
    --cc=fengguang.wu@intel.com \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.