From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1000] memory access overflow in skeleton_rawdev
Date: Tue, 04 Oct 2022 19:12:34 +0000 [thread overview]
Message-ID: <bug-1000-3-oIAwWIHvAX@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1000-3@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=1000
David Marchand (david.marchand@redhat.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
CC| |david.marchand@redhat.com
--- Comment #1 from David Marchand (david.marchand@redhat.com) ---
Closing as same report has been opened under bz #999.
*** This bug has been marked as a duplicate of bug 999 ***
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2022-10-04 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 9:14 bugzilla
2022-10-04 19:12 ` 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-1000-3-oIAwWIHvAX@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).