linux-kernel - Re: Kernel falls apart under light memory pressure (i.e. linking vmlinux)

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 for Android: free password hash cracker in your pocket

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

Date:	Sat, 14 May 2011 11:46:00 -0400
From:	Andrew Lutomirski <luto@....edu>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: Kernel falls apart under light memory pressure (i.e. linking vmlinux)

[cc linux-mm]

On Thu, May 12, 2011 at 7:54 AM, Andrew Lutomirski <luto@....edu> wrote:
> On Thu, May 12, 2011 at 1:46 AM, Andi Kleen <andi@...stfloor.org> wrote:
>>> Here's a nice picture of alt-sysrq-m with lots of memory free but the
>>> system mostly hung.  I can still switch VTs.
>>
>> Would rather need backtraces. Try setting up netconsole or crashdump
>> first.
>
> Here are some logs for two different failure mores.
>
> incorrect_oom_kill.txt is an OOM kill when there was lots of available
> swap to use.  AFAICT the kernel should not have OOM killed at all.
>
> stuck_xyz is when the system is wedged with plenty (~300MB) free
> memory but no swap.  The sysrq files are self-explanatory.
> stuck-sysrq-f.txt is after the others so that it won't have corrupted
> the output.  After taking all that data, I waited awhile and started
> getting soft lockup messges.
>
> I'm having trouble reproducing the "stuck" failure mode on my
> lockdep-enabled kernel right now (the OOM kill is easy), so no lock
> state trace.  But I got one yesterday and IIRC it showed a few tty
> locks and either kworker or kcryptd holding (kqueue) and
> ((&io->work)).
>
> I compressed the larger files.
>
> --Andy
--
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/