[Bugme-janitors] [Bug 9182] Critical memory leak (dirty pages)

bugme-daemon at bugzilla.kernel.org bugme-daemon at bugzilla.kernel.org
Wed Dec 19 15:59:34 PST 2007


http://bugzilla.kernel.org/show_bug.cgi?id=9182





------- Comment #59 from olel at ans.pl  2007-12-19 15:59 -------


On Wed, 19 Dec 2007, Linus Torvalds wrote:

>
>
> On Wed, 19 Dec 2007, Krzysztof Oledzki wrote:
>>
>> Little different call trace:
>
> They're still all very similar, ie it's always about that normal truncate
> path - the details just differ about exactly what causes the truncate.

OK. What still beates me is why this commit:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=fba2591bf4e418b6c3f9f8794c9dd8fe40ae7bd9
exposed the problem?

> I committed the patch witha slightly extended comment and without the
> WARN_ON().

Thank you very much! Is it possible and safe to backport this patch to 
2.6.23 and 2.6.22?

> But it would be great to verify that this really fixes it, and that 
> there isn't some *other* leak. So please keep running the kernel with 
> the patch, and try to make your dirty page leak happen, and see if it 
> really is gone now...
>
> Just to verify that there isn't something else going on too...

So far it is OK:

ole at cougar:~$ uptime;sync;sleep 1;sync;sleep 1;sync;grep Dirt /proc/meminfo
  00:46:42 up  1:56,  1 user,  load average: 0.24, 0.53, 0.61
Dirty:               0 kB

I'll let you know if something happens.

Best regards,

                        Krzysztof Olêdzki


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the Bugme-janitors mailing list