From: Claudio Fontana <cfontana@suse.de>
To: dev@dpdk.org
Cc: Claudio Fontana <cfontana@suse.de>
Subject: [PATCH 0/2] vhost fixes for OVS SIGSEGV in PMD
Date: Mon, 1 Aug 2022 13:53:18 +0200 [thread overview]
Message-ID: <20220801115320.17186-1-cfontana@suse.de> (raw)
Hi, the real meat is in patch 1/2,
which fixes a segmentation fault in the OVS PMD thread when
resynchronizing with QEMU after the guest application has been killed
with SIGKILL.
This fixes an issue where the guest DPDK application is able
to crash the OVS process on the host.
Patch 2/2 is just an improvement in the current error handling.
For your review and comments,
Claudio
Claudio Fontana (2):
vhost: fix error handling in virtio_dev_tx_split
vhost: improve error handling in desc_to_mbuf
lib/vhost/virtio_net.c | 16 +++++++++++++---
1 file changed, 13 insertions(+), 3 deletions(-)
--
2.26.2
next reply other threads:[~2022-08-01 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 11:53 Claudio Fontana [this message]
2022-08-01 11:53 ` [PATCH 1/2] vhost: fix error handling in virtio_dev_tx_split Claudio Fontana
2022-08-01 11:53 ` [PATCH 2/2] vhost: improve error handling in desc_to_mbuf Claudio Fontana
-- strict thread matches above, loose matches on Subject: below --
2022-07-31 20:17 [PATCH 0/2] vhost fixes for OVS SIGSEGV in PMD Claudio Fontana
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=20220801115320.17186-1-cfontana@suse.de \
--to=cfontana@suse.de \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).