From: Shannon Nelson <sln@onemain.com>
To: Anand Khoje <anand.a.khoje@oracle.com>,
Brett Creeley <brett.creeley@amd.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Abhijit Gangurde <abhijit.gangurde@amd.com>,
Leon Romanovsky <leon@kernel.org>,
Eric Joyner <eric.joyner@amd.com>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Kees Cook <kees@kernel.org>, Mohammad Heib <mheib@redhat.com>,
Jacob Keller <jacob.e.keller@intel.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net-next v2] net/ionic: avoid OOB TX partner lookup for hwstamp RXQ
Date: Wed, 12 Aug 2026 22:52:19 -0700 [thread overview]
Message-ID: <5c7cf96a-74a6-46c2-bde3-f39b25a2d09e@onemain.com> (raw)
In-Reply-To: <20260813051315.430146-1-anand.a.khoje@oracle.com>
On 8/12/26 22:13, Anand Khoje wrote:
> The dedicated hardware timestamp RX queue is allocated with q->index
> equal to lif->ionic->nrxqs_per_lif. The normal txqcqs array only
> contains the regular queue pairs, so using that index to set rxq->partner
> can read one entry past txqcqs[] and then write through the derived
> pointer.
> Only link RX/TX partners for normal queue-pair indexes. Leave the hwstamp
> RX queue unpaired, and make the XDP_TX path abort cleanly if an RX queue
> has no TX partner.
>
> Fixes: 8eeed8373e1c ("ionic: Add XDP_TX support")
> Signed-off-by: Anand Khoje <anand.a.khoje@oracle.com>
> Reviewed-by: Si-Wei Liu <si-wei.liu@oracle.com>
> ---
> v2:
> Fixed the Fixes tag.
>
> drivers/net/ethernet/pensando/ionic/ionic_lif.c | 14 ++++++++++++++
> drivers/net/ethernet/pensando/ionic/ionic_txrx.c | 5 ++++-
> 2 files changed, 20 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/pensando/ionic/ionic_lif.c b/drivers/net/ethernet/pensando/ionic/ionic_lif.c
> index fd3ee9820531..1822361e1070 100644
> --- a/drivers/net/ethernet/pensando/ionic/ionic_lif.c
> +++ b/drivers/net/ethernet/pensando/ionic/ionic_lif.c
> @@ -920,9 +920,23 @@ static int ionic_lif_rxq_init(struct ionic_lif *lif, struct ionic_qcq *qcq)
> };
> int err;
>
> + q->partner = NULL;
> +
> + /* Only normal RX queues have matching TX queue partners,
> + * skip partner pairing for hwstamp RX queue.
> + */
> + if (q->index >= lif->nxqs)
> + goto skip_partner;
> +
> + if (WARN_ON_ONCE(!lif->txqcqs ||
> + q->index >= lif->ionic->ntxqs_per_lif ||
> + !lif->txqcqs[q->index]))
> + return -EINVAL;
This driver doesn't have any other WARN type statements, and the WARN*
is more often frowned upon now that so many places use
panic_on_warn. The other place where this kind of check is done simply
prints a dev_err() and returns -ENXIO - see ionic_txrx_enable(). Brett
or Eric J might have another opinion, but you might stick with that
practice here.
> +
> q->partner = &lif->txqcqs[q->index]->q;
> q->partner->partner = q;
>
> +skip_partner:
> if (!lif->xdp_prog ||
> (lif->xdp_prog->aux && lif->xdp_prog->aux->xdp_has_frags))
> ctx.cmd.q_init.flags |= cpu_to_le16(IONIC_QINIT_F_SG);
> diff --git a/drivers/net/ethernet/pensando/ionic/ionic_txrx.c b/drivers/net/ethernet/pensando/ionic/ionic_txrx.c
> index 301ebee2fdc5..73998d61593 100644
> --- a/drivers/net/ethernet/pensando/ionic/ionic_txrx.c
> +++ b/drivers/net/ethernet/pensando/ionic/ionic_txrx.c
> @@ -543,13 +543,18 @@ static bool ionic_run_xdp(struct ionic_rx_stats *stats,
> break;
>
> case XDP_TX:
> + txq = rxq->partner;
> + if (unlikely(!txq)) {
> + err = -EIO;
> + break;
> + }
> +
> xdpf = xdp_convert_buff_to_frame(&xdp_buf);
> if (!xdpf) {
> err = -ENOSPC;
> break;
> }
>
> - txq = rxq->partner;
> nq = netdev_get_tx_queue(netdev, txq->index);
> __netif_tx_lock(nq, smp_processor_id());
> txq_trans_cond_update(nq);
Other than the above, this looks fine to me.
Reviewed-by: Shannon Nelson <sln@onemain.com>
next prev parent reply other threads:[~2026-08-13 6:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 5:13 [PATCH net-next v2] net/ionic: avoid OOB TX partner lookup for hwstamp RXQ Anand Khoje
2026-08-13 5:52 ` Shannon Nelson [this message]
[not found] ` <DM4PR10MB61118B1CBA5845B1502EA476C5DB2@DM4PR10MB6111.namprd10.prod.outlook.com>
2026-08-14 17:31 ` Jakub Kicinski
2026-08-17 16:47 ` Creeley, Brett
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=5c7cf96a-74a6-46c2-bde3-f39b25a2d09e@onemain.com \
--to=sln@onemain.com \
--cc=abhijit.gangurde@amd.com \
--cc=anand.a.khoje@oracle.com \
--cc=andrew+netdev@lunn.ch \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.joyner@amd.com \
--cc=jacob.e.keller@intel.com \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mheib@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=vadim.fedorenko@linux.dev \
/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