From: Michal Hocko <mhocko@suse.com>
To: 陈冠有 <chenguanyou9338@gmail.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Kees Cook <keescook@chromium.org>,
lukas.bulwahn@gmail.com, vbabka@suse.cz, gpiccoli@canonical.com,
chenguanyou <chenguanyou@xiaomi.com>
Subject: Re: [PATCH] hungtask: add filter kthread/check comm
Date: Fri, 21 May 2021 10:31:50 +0200 [thread overview]
Message-ID: <YKdv9hmRh+VxJrnH@dhcp22.suse.cz> (raw)
In-Reply-To: <CAHS3RMVYbHTzD6JnOmE331qSbcnvuYnBe0jraNuuLc0Z2NnStg@mail.gmail.com>
On Fri 21-05-21 14:38:06, 陈冠有 wrote:
> when we no skip kthread, exp log:
> 3,25164,832483138,-; (1)[67:khungtaskd]INFO: task amms_task:51 blocked for
> more than 120 seconds.
> 3,25165,832483169,-; (1)[67:khungtaskd] Tainted: P S W O
> 4.14.186-g9d5f2ff-dirty #4
> 3,25166,832483186,-; (1)[67:khungtaskd]"echo 0 >
> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> 6,25167,832483205,-; (1)[67:khungtaskd]amms_task D 0 51 2
> 0x00000000
> 4,25168,832483232,-; (1)[67:khungtaskd]Call trace:
> 4,25169,832483268,-; (1)[67:khungtaskd] __switch_to+0x134/0x150
> 4,25170,832483297,-; (1)[67:khungtaskd] __schedule+0xd5c/0x1100
> 4,25171,832483318,-; (1)[67:khungtaskd] schedule+0x70/0x90
> 4,25172,832483343,-; (1)[67:khungtaskd] kthread+0xfc/0x18c
> 4,25173,832483365,-; (1)[67:khungtaskd] ret_from_fork+0x10/0x18
> 3,25174,832483482,-; (1)[67:khungtaskd]INFO: task mdrt_thread:123 blocked
> for more than 120 seconds.
> 3,25175,832483501,-; (1)[67:khungtaskd] Tainted: P S W O
> 4.14.186-g9d5f2ff-dirty #4
> 3,25176,832483516,-; (1)[67:khungtaskd]"echo 0 >
> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> 6,25177,832483533,-; (1)[67:khungtaskd]mdrt_thread D 0 123 2
> 0x00000000
> 4,25178,832483555,-; (1)[67:khungtaskd]Call trace:
> 4,25179,832483574,-; (1)[67:khungtaskd] __switch_to+0x134/0x150
> 4,25180,832483595,-; (1)[67:khungtaskd] __schedule+0xd5c/0x1100
> 4,25181,832483615,-; (1)[67:khungtaskd] schedule+0x70/0x90
> 4,25182,832483635,-; (1)[67:khungtaskd] kthread+0xfc/0x18c
> 4,25183,832483655,-; (1)[67:khungtaskd] ret_from_fork+0x10/0x18
> 3,25184,832483737,-; (1)[67:khungtaskd]INFO: task scp_power_reset:227
> blocked for more than 120 seconds.
What are all these kernel threads doing and why it is ok to inhibit them
in the report.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2021-05-21 8:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 12:13 chenguanyou
2021-05-19 13:06 ` Michal Hocko
2021-05-19 17:53 ` Randy Dunlap
[not found] ` <CAHS3RMVYbHTzD6JnOmE331qSbcnvuYnBe0jraNuuLc0Z2NnStg@mail.gmail.com>
2021-05-21 8:31 ` Michal Hocko [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-21 13:25 chenguanyou
2021-05-22 21:51 ` Andrew Morton
[not found] ` <CAHS3RMWjuB98TzvcYyQ0qtNYOxDeM7W1YmyqDYs=H-cn-VsVdw@mail.gmail.com>
2021-05-25 7:26 ` Michal Hocko
2021-05-21 13:25 chenguanyou
2021-05-21 16:37 ` Randy Dunlap
2021-05-18 11:16 chenguanyou
2021-05-19 11:28 ` Vlastimil Babka
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=YKdv9hmRh+VxJrnH@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=chenguanyou9338@gmail.com \
--cc=chenguanyou@xiaomi.com \
--cc=gpiccoli@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=rdunlap@infradead.org \
--cc=vbabka@suse.cz \
/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
all inboxes | Powered by JetHome®