Critical memory leak (dirty pages)
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 19 lines · On Sun, 16 Dec 2007, [email protected] wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=9182
------- Comment #39 from [email protected] 2007-12-16 01:58 -------
Quoted 7 lines
So:
- 2.6.20-rc1: OK
- 2.6.20-rc1-git8 withfba2591bf4e418b6c3f9f8794c9dd8fe40ae7bd9reverted: OK
- 2.6.20-rc1-git8: very BAD
- 2.6.20-rc2: very BAD
- 2.6.20-rc4: very BAD
- >= 2.6.20: BAD (but not *very* BAD!)based on the great info you already acquired, you should be able to bisect this rather effectively, via:
Quoted 8 lines
2.6.20-rc1-git8 ==
921320210bd2ec4f17053d283355b73048ac0e56$ git-bisect start $ git-bisect bad 921320210bd2ec4f17053d283355b73048ac0e56 $ git-bisect good v2.6.20-rc1 Bisecting: 133 revisions left to test after thisso about 7-8 bootups would pinpoint the breakage.
Except that I have very limited time where I can do my tests on this host. Please also note that it takes about ~2h after a reboot, to be 100% sure. So, 7-8 bootups => 14-16h. :|
Quoted 2 lines
It would likely pinpoint
fba2591b, so it would perhaps be best to first attempt a revert offba2591bon a recent kernel.
I wish I could: :(
ole@cougar:/usr/src/linux-2.6.23.9$ cat ..p1 |patch -p1 --dry-run -R patching file fs/hugetlbfs/inode.c Hunk #1 succeeded at 203 (offset 27 lines). patching file include/linux/page-flags.h Hunk #1 succeeded at 262 (offset 9 lines). patching file mm/page-writeback.c Hunk #1 succeeded at 903 (offset 58 lines). patching file mm/truncate.c Unreversed patch detected! Ignore -R? [n] y Hunk #1 succeeded at 52 with fuzz 2 (offset 1 line). Hunk #2 FAILED at 85. Hunk #3 FAILED at 365. Hunk #4 FAILED at 400. 3 out of 4 hunks FAILED -- saving rejects to file mm/truncate.c.rej
Best regards,
Krzysztof Olędzki