linux-kernel - Re: OOM in 2.6.19-rc*

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 11 Nov 2006 18:38:05 +0000 (GMT)
From:	Christian Kujau <evil@...ouse.de>
To:	Adrian Bunk <bunk@...sta.de>
cc:	linux-kernel@...r.kernel.org
Subject: Re: OOM in 2.6.19-rc*

On Sat, 11 Nov 2006, Adrian Bunk wrote:
> Can you test whether an older kernel (preferably the one that worked
> before) shows the same problem?

I could try 2.6.17...but currently I don't know how to reproduce the OOM 
condition - so I'd have to wait 24h until *something* happens and the 
OOM killer kicks in.

> This way you might know whether it's a kernel problem or a distribution
> problem.

I think I'm more interested as to why the OOM killer seems to kill 
innocent apps at random. I can imagine that it's not easy for the kernel 
to tell which userland-application is using up too much memory. Hm, 
egrep -r "OOM|ut of memory" Documentation/    does not reveal much :(

Thanks,
Christian.
-- 
BOFH excuse #362:

Plasma conduit breach
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/