From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: Dmitry Vyukov <dvyukov@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Hocko <mhocko@kernel.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: Fri, 7 Sep 2018 19:49:42 +0900 [thread overview]
Message-ID: <f9f75daf-beb1-0f74-9ff3-dcea3fae44ed@i-love.sakura.ne.jp> (raw)
In-Reply-To: <CACT4Y+bS+kqf+8fp11qSpQ4WtaZt_sVYmvwi_9LFX_=Dwk1N4A@mail.gmail.com>
On 2018/09/07 18:36, Dmitry Vyukov wrote:
> But I am still concerned as to what has changed recently. Potentially
> this happens only on linux-next, at least that's where I saw all
> existing reports.
> New tasks seem to be added to the tail of the tasks list, but this
> part does not seem to be changed recently in linux-next..
>
As far as dump_tasks() is saying, these tasks are alive. Thus, I want to know
what these tasks are doing (i.e. SysRq-t output). Since this is occurring in
linux-next, we can try CONFIG_DEBUG_AID_FOR_SYZBOT=y case like
https://lkml.org/lkml/2018/9/3/353 does.
next prev parent reply other threads:[~2018-09-07 11:24 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
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 [this message]
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=f9f75daf-beb1-0f74-9ff3-dcea3fae44ed@i-love.sakura.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--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