From: Stephen Hemminger <stephen@networkplumber.org>
To: David Ahern <dsahern@gmail.com>
Cc: netdev@vger.kernel.org
Subject: tc f_u32 bug detected
Date: Mon, 29 Mar 2021 22:56:59 -0700 [thread overview]
Message-ID: <20210329225659.568c8700@hermes.local> (raw)
After seeing a user report of trying to use JSON with tc, started to fix some of it.
Found a surprise. The display of U32 filters confuses IPv6 and IPv4. The code in
tc/f_u32.c is obviously wront in print_ipv6(). It is just a copy/past of IPv4.
Almost want to just remove the bad code and let it dump the raw filter.
There is still lots of code missing JSON in the Tc filters. Volunteers and patches needed.
reply other threads:[~2021-03-30 5:57 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=20210329225659.568c8700@hermes.local \
--to=stephen@networkplumber.org \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.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).