From: Oleg Nesterov <oleg@redhat.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Dmitry Vyukov <dvyukov@google.com>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Andrew Morton <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
syzbot <syzbot+f0fc7f62e88b1de99af3@syzkaller.appspotmail.com>,
'Dmitry Vyukov' via syzkaller-upstream-moderation
<syzkaller-upstream-moderation@googlegroups.com>,
linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH] mm, oom: Introduce time limit for dump_tasks duration.
Date: Wed, 12 Sep 2018 18:45:05 +0200 [thread overview]
Message-ID: <20180912164505.GA18706@redhat.com> (raw)
In-Reply-To: <20180911163708.GB27989@redhat.com>
On 09/11, Oleg Nesterov wrote:
>
> On 09/06, Michal Hocko wrote:
> >
> > So a question for Oleg I guess. Is it possible that for_each_process
> > live locks (or stalls for way too long/unbounded amount of time) under
> > heavy fork/exit loads?
>
> Oh yes, it can... plus other problems.
>
> I even sent the initial patches which introduce for_each_process_break/continue
> a long ago... I'll try to find them tommorrow and resend.
Two years ago ;) I don't understand why there were ignored, please see
"[PATCH 0/2] introduce for_each_process_thread_break() and for_each_process_thread_continue()"
I sent a minute ago.
However, I didn't notice that the subject mentions oom/dump_tasks... As for
dump_tasks() it probably doesn't need the new helpers, I'll write another email
tomorrow, but perhaps the time limit is all we need.
Oleg.
next prev parent reply other threads:[~2018-09-12 16:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000004a6b700575178b5a@google.com>
[not found] ` <CACT4Y+aPRGUqAdJCMDWM=Zcy8ZQcHyrsB1ZuWS4VB_+wvLfeaQ@mail.gmail.com>
2018-09-05 10:53 ` INFO: task hung in ext4_da_get_block_prep Tetsuo Handa
2018-09-05 11:06 ` Dmitry Vyukov
2018-09-06 5:53 ` Tetsuo Handa
2018-09-06 9:54 ` Dmitry Vyukov
2018-09-06 10:58 ` [PATCH] mm, oom: Introduce time limit for dump_tasks duration Tetsuo Handa
2018-09-06 11:07 ` Dmitry Vyukov
2018-09-06 11:25 ` Tetsuo Handa
2018-09-06 11:23 ` Michal Hocko
2018-09-06 11:40 ` Tetsuo Handa
2018-09-06 11:53 ` Michal Hocko
2018-09-06 12:08 ` Dmitry Vyukov
2018-09-06 12:16 ` Michal Hocko
2018-09-11 16:37 ` Oleg Nesterov
2018-09-12 16:45 ` Oleg Nesterov [this message]
2018-09-06 13:45 ` Tetsuo Handa
2018-09-06 14:39 ` Michal Hocko
2018-09-06 20:58 ` Tetsuo Handa
2018-09-07 8:27 ` Michal Hocko
2018-09-07 9:36 ` Dmitry Vyukov
2018-09-07 10:49 ` Tetsuo Handa
2018-09-07 11:08 ` Michal Hocko
2018-09-08 14:00 ` Dmitry Vyukov
2018-09-10 14:36 ` Dmitry Vyukov
2018-09-07 10:20 ` Tetsuo Handa
2019-03-03 11:33 ` INFO: task hung in ext4_da_get_block_prep syzbot
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=20180912164505.GA18706@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=rientjes@google.com \
--cc=syzbot+f0fc7f62e88b1de99af3@syzkaller.appspotmail.com \
--cc=syzkaller-upstream-moderation@googlegroups.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;
as well as URLs for NNTP newsgroup(s).