All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1239] VMXNET 3 returned the wrong error code in initializing
Date: Sun, 28 May 2023 10:23:03 +0000	[thread overview]
Message-ID: <bug-1239-3@http.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1239
           Summary: VMXNET 3 returned the wrong error code in initializing
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: Low
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: corezeng@gmail.com
  Target Milestone: ---

To call rte_eth_dev_start() to start a device, this function calls the function
pointer (dev_start) that was registered by the specific device.
rte_eth_dev_start() judges the integer returned from dev_start to continue or
return an error. 

In the driver of VMXNET 3 the vmxnet3_dev_start is the function that needs to
be registered as dev_start, and it called vmxnet3_dev_rxtx_init(). 

In vmxnet3_dev_rxtx_init(), a wrong error code may be thrown after it invokes
vmxnet3_post_rx_bufs() because it negates the error code before returning it*.
It causes rte_eth_dev_start() to give a positive number to the invoker, but it
should be a negative number, as described in the comments.

*: At vmxnet3_rxtx.c:1318

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

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

             reply	other threads:[~2023-05-28 10:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-28 10:23 bugzilla [this message]
2023-06-12 20:55 ` [Bug 1239] VMXNET 3 returned the wrong error code in initializing bugzilla

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-1239-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.