[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)

[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)

[bugzilla]

[-- 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 --]