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, 24 Oct 2019 14:48:06 +0100 [thread overview]
Message-ID: <1693d19e-56c7-9d6f-8e80-10fe82101cff@arm.com> (raw)
In-Reply-To: <0d7aa66d-d2b9-775c-56b3-543d132fdb84@huawei.com>
Hi,
On 14/10/2019 08:03, Zhihao Cheng wrote:
> Hi, everyone. We met a hung task problem while running syzkaller test. The stacks of hung tasks vary in net/fs/sched, and we provide a stable reproduce test case in fs. The higher the kernel version, the lower the probability of reproduce. Maybe the mainline has gradually optimized the scheduling and mutex.
>
> Environment:
> A. qemu(x86_64 8-core 16GB-RAM)
> B. physical machine (x86_64 8-core 314GB-RAM)
>
> ./syz-execprog -executor=/home/abc/syz-executor -repeat=0 -procs=16 -cover=0 repro
> repro is a configuration file containing syzkaller execution instructions, which shown as follows:
> syz_execute_func(&(0x7f0000000140)="f2aa984413e80f059532058300000071f32ef30f1b6f002e676666440f381d953b0000009fcc77a7141e8f6978e394db96000000928640c4e2b140da6c4f086447deecf2460fd6c40f49100045660fc462c0f726448047000040df6e32b8417e10bd61796e91565646bc16442ecbb1a978c33537771656c441add398b50000000feb76f7f7210173dddfc421785a6600a32c9f5d04ecc7c764660f600500040000c4035922770063c4217be62e450f8a0163000021f0c4e25dbe044c31e053b3eb53b3eb890f32d393400f383ca8faffec1f8dbf4feeee1e480404fb2e400f1ad30fae746d00ab07c4a2d538cb0ff803461439f5e3480f5140a3c4c4021bf7e8561eeaea0f6c3dce67460ffd1a000fb2430f12f5c423557904e774")
> socket(0x1, 0x80000, 0x4)
>
I did try to run that but kept hitting cgroup config options that aren't
enabled in my defconfig - I gave up after net_cls, net_prio and the freezer.
Could you please share your .config?
next prev parent reply other threads:[~2019-10-24 13:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 7:03 Zhihao Cheng
2019-10-24 13:48 ` Valentin Schneider [this message]
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
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=1693d19e-56c7-9d6f-8e80-10fe82101cff@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
all inboxes | Powered by JetHome®