linux-kernel - RE: System hang problem.

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-next>] [day] [month] [year] [list]

Date:	Tue, 3 Oct 2006 17:07:25 -0700
From:	"Manish Neema" <Manish.Neema@...opsys.com>
To:	"Keith Mannthey" <kmannth@...il.com>
Cc:	<linux-kernel@...r.kernel.org>
Subject: RE: System hang problem.

Thanks Keith for the response.

My explanation earlier is not clear. The "automount" process dying with
restrictive overcommit settings is not because of the OOM kill. It looks
like some bug with "automount" binary itself causing it to exit when it
could not service a new request.

"cd /remote/something" when the system is out of (allocate'able) memory
causes the below events (obtained from /var/log/messages)

Oct  3 13:35:32 gentoo036 automount[2060]: handle_packet_missing: fork:
Cannot allocate memory
Oct  3 13:35:34 gentoo036 automount[2060]: can't unmount /remote

And then the automount process for /remote mount disappears, which
should not happen.

Thanks anyways, I'll try to take it up with RedHat again...

-Manish 

-
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/