From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 391] The dpdk-devbind.py tool crashes if some NIC property contains a unicode character - Patch proposal
Date: Wed, 05 Feb 2020 18:51:31 +0000 [thread overview]
Message-ID: <bug-391-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=391
Bug ID: 391
Summary: The dpdk-devbind.py tool crashes if some NIC property
contains a unicode character - Patch proposal
Product: DPDK
Version: 19.11
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: pierrick.louin@orange.com
Target Milestone: ---
Created attachment 82
--> https://bugs.dpdk.org/attachment.cgi?id=82&action=edit
Error + Correction patch proposed
Calling the dpdk-devbind.py tool may crash with the following message:
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 17:
ordinal not in range(128)
Actually this happens when one of the network cards shows a non ascii code in
one of its properties.
The failure occurs whether or not the NIC in cause is concerned by the current
action.
Example of a mellanox card with attribute 'Subsystem: Mellanox Technologies
ConnectX®-5'.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-02-05 18:51 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-391-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.