From: Bruce Richardson <bruce.richardson@intel.com>
To: Dawid Wesierski <dawid.wesierski@intel.com>
Cc: <dev@dpdk.org>, <vladimir.medvedkin@intel.com>,
<anatoly.burakov@intel.com>, <marek.kasiewicz@intel.com>
Subject: Re: [PATCH v2 0/3] net/iavf: fix TM hierarchy commit and TM ops without QoS
Date: Tue, 20 Oct 2026 17:56:37 +0100 [thread overview]
Message-ID: <atedRXQvvMrkOl4h@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <cover.1792504817.git.dawid.wesierski@intel.com>
On Tue, Oct 20, 2026 at 03:22:09PM +0000, Dawid Wesierski wrote:
> Three fixes in the iavf traffic manager.
>
> Patch 1 removes a second free of the queue TC map. The fault is in main
> only, after commit f6e33f09f766. No release has it.
>
> Patch 2 sets the queue ID and TC of each queue node in the queue
> bandwidth message. Without it, a queue node with no shaper profile
> resets queue 0, and its own queue keeps the rate limit that the PF
> holds from an earlier process.
>
> Patch 3 returns -ENOTSUP from the TM ops that read qos_cap when the PF
> does not grant VIRTCHNL_VF_OFFLOAD_QOS, for example the in-tree ice PF.
> These ops cause a segmentation fault now.
>
> Tested with testpmd on an E830 VF, out-of-tree ice PF:
> - Patch 1: three hierarchy commits on a started port. Without the
> patch, an ASan build reports a heap-buffer-overflow in rte_free()
> from iavf_hierarchy_commit() at the second commit. With it, there is
> no report, also after port reset and close.
> - Patch 2: one process sets 100 Mbit/s on two queues and exits. The
> next process commits two queue nodes without a shaper profile.
> Without the patch, only queue 0 gets back its full rate. With it,
> both queues do.
> - Patch 3: in-tree ice PF, so the VF has no QoS offload. Without the
> patch, TM capabilities get, shaper profile add and node add give a
> segmentation fault. With it, they return an error.
>
> v2:
> - Patch 1: also remove the rte_free() of the map in iavf_uninit_vf()
> (Bruce Richardson).
> - Patch 2: commit message from Bruce Richardson.
> - Add the Acked-by of Bruce Richardson to the three patches.
> - Rebase on the current next-net-intel.
>
Series applied to dpdk-next-net-intel.
Thanks,
/Bruce
prev parent reply other threads:[~2026-10-20 16:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 12:24 [PATCH 0/3] net/iavf: fix TM hierarchy commit and TM ops without QoS Dawid Wesierski
2026-10-14 12:24 ` [PATCH 1/3] net/iavf: fix invalid free of queue TC map Dawid Wesierski
2026-10-19 16:47 ` Bruce Richardson
2026-10-19 17:06 ` Bruce Richardson
2026-10-20 15:22 ` Dawid Wesierski
2026-10-14 12:24 ` [PATCH 2/3] net/iavf: fix bandwidth config of unshaped queues Dawid Wesierski
2026-10-20 9:33 ` Bruce Richardson
2026-10-20 15:22 ` Dawid Wesierski
2026-10-14 12:24 ` [PATCH 3/3] net/iavf: fix crash in TM ops without QoS capability Dawid Wesierski
2026-10-20 9:50 ` Bruce Richardson
2026-10-20 15:22 ` [PATCH v2 0/3] net/iavf: fix TM hierarchy commit and TM ops without QoS Dawid Wesierski
2026-10-20 15:22 ` [PATCH v2 1/3] net/iavf: fix invalid free of queue TC map Dawid Wesierski
2026-10-20 15:22 ` [PATCH v2 2/3] net/iavf: fix bandwidth config of unshaped queues Dawid Wesierski
2026-10-20 15:22 ` [PATCH v2 3/3] net/iavf: fix crash in TM ops without QoS capability Dawid Wesierski
2026-10-20 16:56 ` Bruce Richardson [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=atedRXQvvMrkOl4h@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dawid.wesierski@intel.com \
--cc=dev@dpdk.org \
--cc=marek.kasiewicz@intel.com \
--cc=vladimir.medvedkin@intel.com \
/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