All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/vhost/virtio Bug 1467] Virtio_user as Exception Path  in secondary  process report mistakes ( virtio_user_notify_queue(): failed to kick backend: Bad file descriptor)
Date: Thu, 20 Jun 2024 02:46:53 +0000	[thread overview]
Message-ID: <bug-1467-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1467

            Bug ID: 1467
           Summary: Virtio_user as Exception Path  in secondary  process
                    report mistakes ( virtio_user_notify_queue(): failed
                    to kick backend: Bad file descriptor)
           Product: DPDK
           Version: 21.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: critical
          Priority: Normal
         Component: vhost/virtio
          Assignee: dev@dpdk.org
          Reporter: 952983126@qq.com
  Target Milestone: ---

when using Virtio_user as Exception Path ,configure the port in the primary
process , virtio_user do rx and tx in the secondary process. it generates a
mistake in tx such as (virtio_user_notify_queue(): failed to kick backend: Bad
file descriptor).

in my opinion ,when initialize the second process , is it properly to copy the
callfd and kickfd  which are initialized by primay process  to the secondary
process ? in this situation ,i don't think  the secondary process could find
the correct kickfd  ,and it make kthread work  abnormal.

please see the question ,thank you !!!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 3206 bytes --]

                 reply	other threads:[~2024-06-20  2:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-1467-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.