public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Valentin Schneider <valentin.schneider@arm.com>
To: Zhihao Cheng <chengzhihao1@huawei.com>,
	LKML <linux-kernel@vger.kernel.org>,
	peterz@infradead.org, Ingo Molnar <mingo@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	patrick.bellasi@arm.com, tglx@linutronix.de
Cc: Kefeng Wang <wangkefeng.wang@huawei.com>,
	"zhangyi (F)" <yi.zhang@huawei.com>
Subject: Re: [QUESTION] Hung task warning while running syzkaller test
Date: Thu, 31 Oct 2019 02:36:42 +0100	[thread overview]
Message-ID: <6d78bdbc-e4f8-7ff7-8445-c9dc07b0614a@arm.com> (raw)
In-Reply-To: <4453942d-c4f2-bbbe-64a9-4313c0fccfbf@huawei.com>

On 29/10/2019 03:25, Zhihao Cheng wrote:
> I don't know much about the freezer mechanism of CGroup, but I tried it. I turned off all the CGroup related config options and reproduced the hung task on a fresh busybox-made root file system. I added rootfs in attachment. So, I guess hung task has nothing to do with CGroup(freezer).
> 

That's good to know, thanks for digging some more. I'm on the move ATM but if
I find some time I'll try to stare some more at the C reproducer.


  parent reply	other threads:[~2019-10-31  1:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14  7:03 [QUESTION] Hung task warning while running syzkaller test Zhihao Cheng
2019-10-24 13:48 ` Valentin Schneider
2019-10-25 12:50   ` Zhihao Cheng
2019-10-25 15:26     ` Valentin Schneider
2019-10-25 15:29     ` Valentin Schneider
     [not found]       ` <abba880d-cfa6-3485-7831-9998db290396@huawei.com>
2019-10-28  1:47         ` Zhihao Cheng
2019-10-28 17:54         ` Valentin Schneider
     [not found]           ` <4453942d-c4f2-bbbe-64a9-4313c0fccfbf@huawei.com>
2019-10-29  9:09             ` Zhihao Cheng
2019-10-31  1:36             ` Valentin Schneider [this message]
2019-11-13 13:55               ` Valentin Schneider

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=6d78bdbc-e4f8-7ff7-8445-c9dc07b0614a@arm.com \
    --to=valentin.schneider@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=chengzhihao1@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=patrick.bellasi@arm.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=wangkefeng.wang@huawei.com \
    --cc=yi.zhang@huawei.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