public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Krzysztof Oledzki <olel@ans.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Nick Piggin <nickpiggin@yahoo.com.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Osterried <osterried@jesse.de>
Subject: Re: [Bug 9182] Critical memory leak (dirty pages)
Date: Thu, 13 Dec 2007 16:44:31 +0100	[thread overview]
Message-ID: <1197560671.6895.17.camel@twins> (raw)
In-Reply-To: <Pine.LNX.4.64.0712131606410.24173@bizon.gios.gov.pl>


On Thu, 2007-12-13 at 16:17 +0100, Krzysztof Oledzki wrote:
> 

> BTW: Could someone please look at this problem? I feel little ignored and 
> in my situation this is a critical regression.

I was hoping to get around to it today, but I guess tomorrow will have
to do :-/

So, its ext3, dirty some pages, sync, and dirty doesn't fall to 0,
right?

Does it happen with other filesystems as well?

What are you ext3 mount options?




  reply	other threads:[~2007-12-13 15:44 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28  8:42 Strange system hangs Krzysztof Oledzki
2007-09-28  9:17 ` Peter Zijlstra
2007-09-28  9:44   ` Krzysztof Oledzki
2007-09-28 20:14 ` Nick Piggin
2007-09-29 15:54   ` Krzysztof Oledzki
2007-10-09 20:08   ` Krzysztof Oledzki
2007-10-16  7:54   ` Krzysztof Oledzki
2007-12-02 15:09   ` Krzysztof Oledzki
     [not found]     ` <200712030936.25363.osterried@jesse.de>
2007-12-13 15:17       ` [Bug 9182] Critical memory leak (dirty pages) Krzysztof Oledzki
2007-12-13 15:44         ` Peter Zijlstra [this message]
2007-12-13 16:16           ` Krzysztof Oledzki
2007-12-15 12:33             ` Krzysztof Oledzki
2007-12-15 21:53               ` Krzysztof Oledzki
     [not found] <20071205135655.1A832108010@picon.linux-foundation.org>
2007-12-05 14:09 ` Krzysztof Oledzki
     [not found] <20071205213750.14194108010@picon.linux-foundation.org>
     [not found] ` <Pine.LNX.4.64.0712052238520.21312@bizon.gios.gov.pl>
     [not found]   ` <Pine.LNX.4.64.0712111844510.21312@bizon.gios.gov.pl>
2007-12-12 13:28     ` Krzysztof Oledzki
     [not found] <20071215221935.306A5108068@picon.linux-foundation.org>
2007-12-15 23:08 ` Krzysztof Oledzki
2007-12-16  4:35   ` Andrew Morton
2007-12-16  9:33     ` Krzysztof Oledzki
2007-12-16  9:51       ` Andrew Morton
2007-12-16 13:46         ` Krzysztof Oledzki
2007-12-16 21:51           ` Andrew Morton
2007-12-17 14:26             ` Jan Kara
2007-12-17 17:17             ` Krzysztof Oledzki
2007-12-19 17:44           ` Linus Torvalds
2007-12-20  1:05             ` Jan Kara
2007-12-20  1:19               ` Nick Piggin
2007-12-20 14:12             ` Björn Steinbrink
2007-12-20 15:04               ` Jan Kara
2007-12-20 16:05                 ` Jan Kara
2007-12-20 16:25               ` Linus Torvalds
2007-12-20 17:25                 ` Jan Kara
2007-12-20 19:24                   ` Linus Torvalds
2007-12-21  1:59                     ` Nick Piggin
2007-12-20 22:28                 ` Björn Steinbrink
2007-12-21 19:59                   ` Krzysztof Oledzki
     [not found] <20071216095834.1B899108069@picon.linux-foundation.org>
2007-12-16 10:12 ` Krzysztof Oledzki

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=1197560671.6895.17.camel@twins \
    --to=peterz@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=olel@ans.pl \
    --cc=osterried@jesse.de \
    /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