From: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Alex Williamson <alex.williamson@redhat.com>,
Leon Romanovsky <leon@kernel.org>
Subject: Re: Write to srvio_numvfs triggers kernel panic
Date: Sat, 7 May 2022 10:25:16 +0000 [thread overview]
Message-ID: <87levdljw3.fsf@epam.com> (raw)
In-Reply-To: <20220507013436.GB63055@ziepe.ca>
Jason Gunthorpe <jgg@ziepe.ca> writes:
> On Fri, May 06, 2022 at 03:17:22PM -0500, Bjorn Helgaas wrote:
>
>> > Modules linked in: xt_MASQUERADE iptable_nat nf_nat nf_conntrack nf_defrag_ipv6
>> > nf_defrag_ipv4 libcrc32c iptable_filter crct10dif_ce nvme nvme_core at24
>> > pci_endpoint_test bridge pdrv_genirq ip_tables x_tables ipv6
>> > CPU: 3 PID: 287 Comm: sh Not tainted 5.10.41-lorc+ #233
>> > Hardware name: XENVM-4.17 (DT)
> ^^^^^^^^^^^^^^^^^
>
>> So this means the VF must have an SR-IOV capability, which sounds a
>> little dubious. From PCIe r6.0:
>
> Enabling SRIOV from within a VM is "exciting" - I would not be
> surprised if there was some wonky bugs here.
Well, yes. But in this case, this VM has direct access to the PCIe
controller. So it should not cause any troubles. I'll try baremetal
setup, though.
--
Volodymyr Babchuk at EPAM
next prev parent reply other threads:[~2022-05-07 10:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 19:56 Write to srvio_numvfs triggers kernel panic Volodymyr Babchuk
2022-05-06 20:17 ` Bjorn Helgaas
2022-05-07 1:34 ` Jason Gunthorpe
2022-05-07 10:25 ` Volodymyr Babchuk [this message]
2022-05-08 11:19 ` Leon Romanovsky
2022-05-09 18:22 ` Keith Busch
2022-05-07 10:22 ` Volodymyr Babchuk
2022-05-07 15:41 ` Bjorn Helgaas
2022-05-08 11:07 ` Volodymyr Babchuk
2022-05-09 16:49 ` Bjorn Helgaas
2022-05-09 16:58 ` Alex Williamson
2022-05-10 6:39 ` Christoph Hellwig
2022-05-10 17:37 ` Bjorn Helgaas
2022-05-12 7:18 ` Volodymyr Babchuk
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=87levdljw3.fsf@epam.com \
--to=volodymyr_babchuk@epam.com \
--cc=alex.williamson@redhat.com \
--cc=helgaas@kernel.org \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-pci@vger.kernel.org \
/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