From: "Michael S. Tsirkin" <mst@redhat.com>
To: Wenli Quan <wquan@redhat.com>
Cc: "Dragos Tatulea" <dtatulea@nvidia.com>,
"Jason Wang" <jasowang@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
virtualization@lists.linux.dev
Subject: Re: Host Crash When creating a vDPA Device with device_features
Date: Thu, 3 Jul 2025 02:47:09 -0400 [thread overview]
Message-ID: <20250703024601-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CADZSLS0r78HhZAStBaN1evCSoPqRJU95Lt8AqZNJ6+wwYQ6vPQ@mail.gmail.com>
On Thu, Jul 03, 2025 at 11:58:26AM +0800, Wenli Quan wrote:
> Hello all:
>
> I am reporting a issue where the host system crashed when attempting to add a
> vDPA device using the command:
>
> # uname -r
>
> 6.16.0-rc2
>
> # modprobe vdpa
>
> # modprobe vhost-vdpa
>
> # modprobe mlx5-vdpa
>
> # echo 1 > /sys/class/net/ens7f1np1/device/sriov_numvfs
>
> # lspci |grep -i Mell
>
> 61:00.0 Ethernet controller: Mellanox Technologies MT43244 BlueField-3
> integrated ConnectX-7 network controller (rev 01)
>
> 61:00.1 Ethernet controller: Mellanox Technologies MT43244 BlueField-3
> integrated ConnectX-7 network controller (rev 01)
>
> 61:00.2 DMA controller: Mellanox Technologies MT43244 BlueField-3 SoC
> Management Interface (rev 01)
>
> b5:00.0 Ethernet controller: Mellanox Technologies MT2892 Family [ConnectX-6
> Dx]
>
> b5:00.1 Ethernet controller: Mellanox Technologies MT2892 Family [ConnectX-6
> Dx]
>
> b5:03.2 Ethernet controller: Mellanox Technologies ConnectX Family mlx5Gen
> Virtual Function
>
> #vdpa dev add name vdpa0 mgmtdev pci/0000:b5:03.2 device_features 0x300c31829
>
>
> Then the host creatshed, please check the crash dump in attachment.
>
....
Thanks a lot for the report! How reproducible is this? Bisectable to
a specific commit?
--
MST
next prev parent reply other threads:[~2025-07-03 6:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 3:58 Host Crash When creating a vDPA Device with device_features Wenli Quan
2025-07-03 6:47 ` Michael S. Tsirkin [this message]
2025-07-03 14:17 ` Dragos Tatulea
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=20250703024601-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dtatulea@nvidia.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=wquan@redhat.com \
--cc=xuanzhuo@linux.alibaba.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