From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: syzbot <syzbot+d0fc9d3c166bc5e4a94b@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, mhocko@kernel.org
Cc: ebiederm@xmission.com, guro@fb.com, hannes@cmpxchg.org,
jglisse@redhat.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, shakeelb@google.com,
syzkaller-bugs@googlegroups.com, yuzhoujian@didichuxing.com
Subject: Re: general protection fault in oom_unkillable_task
Date: Sun, 16 Jun 2019 00:59:32 +0900 [thread overview]
Message-ID: <8c50ca8c-3869-6f50-3a3f-bc7726c39975@i-love.sakura.ne.jp> (raw)
In-Reply-To: <cc3d5247-855d-a124-041f-64c4659d95c3@i-love.sakura.ne.jp>
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...
next prev parent reply other threads:[~2019-06-15 16:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-15 1:08 syzbot
2019-06-15 1:10 ` Tetsuo Handa
2019-06-15 15:59 ` Tetsuo Handa [this message]
2019-06-15 3:15 ` Shakeel Butt
2019-06-15 13:49 ` Michal Hocko
2019-06-15 16:11 ` Shakeel Butt
2019-06-15 16:48 ` Tetsuo Handa
2019-06-15 18:50 ` Shakeel Butt
2019-06-15 21:33 ` Tetsuo Handa
2019-06-16 7:37 ` Tetsuo Handa
2019-06-16 15:13 ` Tetsuo Handa
2019-06-17 6:31 ` Michal Hocko
2019-06-17 13:23 ` Shakeel Butt
2019-06-18 1:45 ` Andrew Morton
2019-06-18 4:21 ` Shakeel Butt
2019-06-17 6:33 ` Michal Hocko
2019-06-17 9:56 ` Tetsuo Handa
2019-06-17 10:13 ` Michal Hocko
2019-06-16 5:48 ` Hillf Danton
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=8c50ca8c-3869-6f50-3a3f-bc7726c39975@i-love.sakura.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=shakeelb@google.com \
--cc=syzbot+d0fc9d3c166bc5e4a94b@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yuzhoujian@didichuxing.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox