From: Jens Axboe <axboe@kernel.dk>
To: Pengfei Xu <pengfei.xu@intel.com>,
Pavel Begunkov <asml.silence@gmail.com>
Cc: linux-kernel@vger.kernel.org, heng.su@intel.com
Subject: Re: [Syzkaller & bisect] There is "io_ring_exit_work" related Call Trace in v5.2-rc5 kernel
Date: Thu, 2 Feb 2023 12:44:47 -0700 [thread overview]
Message-ID: <fb27661f-59dd-98cd-203a-8fa86dc209d4@kernel.dk> (raw)
In-Reply-To: <Y9t6tflIcFPy84S5@xpf.sh.intel.com>
On 2/2/23 1:56 AM, Pengfei Xu wrote:
> Hi Pavel Begunkov,
>
> On 2023-02-01 at 15:52:47 +0000, Pavel Begunkov wrote:
>> On 1/28/23 14:49, Pavel Begunkov wrote:
>>> On 1/28/23 08:44, Pengfei Xu wrote:
>>>> Hi Pavel Begunkov and kernel expert,
>>>>
>>>> Greeting!
>>>>
>>>> There is "io_ring_exit_work" related Call Trace in v5.2-rc5 kernel in guest
>>>> on Sapphire Rapids server.
>>>
>>> Thanks for the report, we'll take a look
>>
>> Not reproducible for me. Apparently, the repro creates a normal ring
>> and immediately closes it, then io_ring_exit_work() hangs waiting to
>> the task to execute task_work.
> Ah, I put the reproduced virtual machine in gitlab.
> git clone https://gitlab.com/xupengfe/repro_vm_env.git
> cd repro_vm_env
> tar -xvf repro_vm_env.tar.gz
> cd repro_vm_env; ./start3.sh // it needs qemu-system-x86_64 and I used v7.1.0
> //start3.sh will load bzImage_2241ab53cbb5cdb08a6b2d4688feb13971058f65 v6.2-rc5 kernel
> In vm and login with root, there is no password for root.
> After login vm successfully, ./repro to reproduce this issue.
> It could be reproduced in about 6min.
>
> If you already have qemu-system-x86_64, please ignore below info.
> If you want to install qemu v7.1.0 version,
> git clone https://github.com/qemu/qemu.git
> cd qemu
> git checkout -f v7.1.0
> mkdir build
> cd build
> yum install -y ninja-build.x86_64
> ../configure --target-list=x86_64-softmmu --enable-kvm --enable-vnc --enable-gtk --enable-sdl
> make
> make install
> Done.
Are you sure you attached the right kconfig in the initial report? It
is from 5.18.x.
--
Jens Axboe
next prev parent reply other threads:[~2023-02-02 19:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 8:44 [Syzkaller & bisect] There is "io_ring_exit_work" related Call Trace in v5.2-rc5 kernel Pengfei Xu
2023-01-28 8:52 ` [Syzkaller & bisect] There is "io_ring_exit_work" related Call Trace in v6.2-rc5 kernel Pengfei Xu
2023-01-28 14:49 ` [Syzkaller & bisect] There is "io_ring_exit_work" related Call Trace in v5.2-rc5 kernel Pavel Begunkov
2023-02-01 15:52 ` Pavel Begunkov
2023-02-02 8:56 ` Pengfei Xu
2023-02-02 19:44 ` Jens Axboe [this message]
2023-02-02 20:37 ` Jens Axboe
2023-02-03 2:08 ` 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=fb27661f-59dd-98cd-203a-8fa86dc209d4@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=heng.su@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pengfei.xu@intel.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;
as well as URLs for NNTP newsgroup(s).