linux-kernel - Re: general protection fault in oom_unkillable

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]

Message-ID: <8c50ca8c-3869-6f50-3a3f-bc7726c39975@i-love.sakura.ne.jp>
Date:   Sun, 16 Jun 2019 00:59:32 +0900
From:   Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
To:     syzbot <syzbot+d0fc9d3c166bc5e4a94b@...kaller.appspotmail.com>,
        akpm@...ux-foundation.org, mhocko@...nel.org
Cc:     ebiederm@...ssion.com, guro@...com, hannes@...xchg.org,
        jglisse@...hat.com, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org, shakeelb@...gle.com,
        syzkaller-bugs@...glegroups.com, yuzhoujian@...ichuxing.com
Subject: Re: general protection fault in oom_unkillable_task

On 2019/06/15 10:10, Tetsuo Handa wrote:
> I'm not sure this patch is correct/safe. Can you try memcg OOM torture
> test (including memcg group OOM killing enabled) with this patch applied?

Well, I guess this patch was wrong. The ordering of removing threads
does not matter as long as we start traversing via signal_struct.
The reason why crashed at for_each_thread() is unknown...