From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 943] BUG: scheduling while atomic
Date: Fri, 15 Dec 2023 03:55:38 +0000 [thread overview]
Message-ID: <bug-943-3-dR8IWZDXno@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-943-3@http.bugs.dpdk.org/>
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=943
Stephen Hemminger (stephen@networkplumber.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
CC| |stephen@networkplumber.org
Status|CONFIRMED |RESOLVED
--- Comment #1 from Stephen Hemminger (stephen@networkplumber.org) ---
KNI was flawed in the design. It called to userspace with RTNL mutex held
leading to all sorts of issues. Because of this and other flaws, the driver was
deprecated and removed in 23.11 release. Closing this bug.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2890 bytes --]
prev parent reply other threads:[~2023-12-15 3:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 8:44 bugzilla
2022-03-01 16:55 ` Stephen Hemminger
2023-12-15 3:55 ` bugzilla [this message]
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-943-3-dR8IWZDXno@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 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).