From: Pengfei Xu <pengfei.xu@intel.com>
To: <linux-kernel@vger.kernel.org>, <mszeredi@redhat.com>
Cc: <heng.su@intel.com>
Subject: Re: [Syzkaller] INFO: task hung in fuse_lookup with v6.0 kernel in guest
Date: Tue, 18 Oct 2022 09:37:33 +0800 [thread overview]
Message-ID: <Y04DXT9JbwpeRDex@xpf.sh.intel.com> (raw)
In-Reply-To: <Y00b31dX1mIfgnBP@xpf.sh.intel.com>
Hi,
I received the email that:"BOUNCE linux-kernel@vger.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.
next parent reply other threads:[~2022-10-18 1:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Y00b31dX1mIfgnBP@xpf.sh.intel.com>
2022-10-18 1:37 ` Pengfei Xu [this message]
2022-10-18 9:23 ` [Syzkaller] INFO: task hung in fuse_lookup with v6.0 kernel in guest Miklos Szeredi
2022-10-19 2:53 ` Pengfei Xu
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=Y04DXT9JbwpeRDex@xpf.sh.intel.com \
--to=pengfei.xu@intel.com \
--cc=heng.su@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@redhat.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