[<prev] [next>] [day] [month] [year] [list]
Message-ID: <Y04DXT9JbwpeRDex@xpf.sh.intel.com>
Date: Tue, 18 Oct 2022 09:37:33 +0800
From: Pengfei Xu <pengfei.xu@...el.com>
To: <linux-kernel@...r.kernel.org>, <mszeredi@...hat.com>
CC: <heng.su@...el.com>
Subject: Re: [Syzkaller] INFO: task hung in fuse_lookup with v6.0 kernel in
guest
Hi,
I received the email that:"BOUNCE linux-kernel@...r.kernel.org: Message too
long (>6000000 chars)".
To avoid missing the attached log, I put all the info in below link:
https://github.com/xupengfe/syzkaller_logs/tree/main/221017_task_hung_in_fuse_lookup
It's reproduced in v6.0 mainline guest on TGL-H platform.
The dmesg that reproduces the issue with the v6.0 kernel in the guest is also
in the link above.
Thanks!
BR.
On 2022-10-17 at 17:09:51 +0800, Pengfei Xu wrote:
> Hi Miklos,
>
> Greeting!
>
> Platform: Tiger lake CPU platform.
>
> We found 1 "task hung in fuse_lookup" issue by syzkaller with v6.0 mainline
> kernel in guest.
>
> Bisected and found the bad commit:
> "
> commit: 62dd1fc8cc6b22e3e568be46ebdb817e66f5d6a5
> fuse: move fget() to fuse_get_tree()
> "
>
> Reproduced code generated by syzkaller, binary, bisect log and all the dmesg
> info are in attached package.
>
> Hope it's helpful.
>
> Thanks!
> BR.
Powered by blists - more mailing lists