Re: Linux 2.4.23-rc5
From: Ihar 'Philips' Filipau
Date: Tue Nov 25 2003 - 11:39:57 EST
Hi!
I was investigating memory allocation problems on my systems.
And I only figured out that I'm using quite up-to-date kernel - 2.4.22.
This is my post from another thread:
Vanilla 2.4.22 (this is x86) (with HZ=1024, if it does matter).
after '# echo -1 >/proc/sys/vm/overcommit_memory'
1. test app with memory touch still gets killed by
oom_killer. (so no malloc() == NULL)
2. test app w/o memory touch still can happily allocate 2.8GB
of memory (x86 - looks like 3/1 memory split) and only then
gets NULL pointer - oom_killer is silent.
"overcommit_memory < 0" supposed to not allow apps to overallocate
memory - but still it works not like it is said in
Documentation/filesystems/proc.txt.
So apps which try to be MM friendly can silently break due to
very-very lazy memory allocation in kernel. Not nice when malloc() says
"everything is fine!".
[ Just checked: with overcommit==-1, as soon app trying to touch
those magic 2.8GB of memory, it gets killed by oom_killer. This is
totally wrong... ]
Probably fix docs at least... :-(
Marcelo Tosatti wrote:
Hi,
Yet another thing showed up (possible data corruption on x86-64), so here
goes -rc5.
Summary of changes from v2.4.23-rc4 to v2.4.23-rc5
============================================
Andi Kleen:
o Fix 32bit truncate64 on x86-64
Marcelo Tosatti:
o Felix Radensky: Remove debugging printk from agpgart
o Changed EXTRAVERSION to -rc5
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/