From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] system freezes when using swap that is encrypted
Date: Sun, 14 Nov 2010 14:08:27 +0100 [thread overview]
Message-ID: <20101114130827.GA666@tansi.org> (raw)
In-Reply-To: <20101113170109.GA6865@fancy-poultry.org>
On Sat, Nov 13, 2010 at 06:01:09PM +0100, Heinz Diehl wrote:
> On 13.11.2010, Arno Wagner wrote:
>
> > I don't know what criteria lead to activation of the OOM killer,
> [....]
>
> How do you know it gets OOM-killed?
I don't. By Occams Razor it is just my first suspected cause.
Reason is that (if I understand correctly) all the memory
has been allocated before the crash, so a NULL response
from malloc is not the cause. But other than an unrelated
program crash, that basically leaves the OOM killer.
AFAIK shell (vm) limits block the allocation but do
not SIGTERM/SIGKILL the process.
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2010-11-14 13:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 15:17 [dm-crypt] system freezes when using swap that is encrypted Nicolas Bock
2010-11-12 16:49 ` dave b
2010-11-12 16:51 ` Arno Wagner
2010-11-12 18:23 ` Nicolas Bock
2010-11-12 19:32 ` Nicolas Bock
2010-11-12 21:01 ` Milan Broz
2010-11-13 3:40 ` Nicolas Bock
2010-11-13 14:53 ` Arno Wagner
2010-11-13 17:01 ` Heinz Diehl
2010-11-13 17:02 ` Heinz Diehl
2010-11-14 13:08 ` Arno Wagner [this message]
2010-11-14 15:28 ` dave b
2010-11-13 18:49 ` Nicolas Bock
2010-11-14 0:35 ` Carlo Wood
2010-11-14 8:23 ` Milan Broz
2010-11-14 7:54 ` Heinz Diehl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101114130827.GA666@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.