From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1664] rte_ipv6_addr_is_v4mapped wrong logic
Date: Tue, 18 Feb 2025 21:04:30 +0000 [thread overview]
Message-ID: <bug-1664-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1664
Bug ID: 1664
Summary: rte_ipv6_addr_is_v4mapped wrong logic
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: sunnylandh@gmail.com
Target Milestone: ---
rte_ipv6_addr_is_v4mapped() is implemented by comparing the first 32 bits of an
IPv6 address with the ::ffff:0.0.0.0/96 prefix.
https://git.dpdk.org/dpdk/tree/lib/net/rte_ip6.h?id=fba9875559906e04eaeb74532f4cfd51194259a2#n313
The following snippet prints "1", but the loopback address is not a v4mapped
address.
#include <stdio.h>
#include <rte_ip6.h>
int main() {
struct rte_ipv6_addr a = RTE_IPV6_ADDR_LOOPBACK;
printf("%d\n", rte_ipv6_addr_is_v4mapped(&a));
}
The function should compare the first 96 bits instead.
rte_ipv6_addr_is_v4compat() has the same mistake.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3146 bytes --]
reply other threads:[~2025-02-18 21:04 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-1664-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 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).