Netdev List
 help / color / mirror / Atom feed
From: Subrat Pandey <subratp@marvell.com>
To: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>
Cc: <pabeni@redhat.com>, <kuba@kernel.org>, <edumazet@google.com>,
	<davem@davemloft.net>, <andrew+netdev@lunn.ch>,
	<sbhatta@marvell.com>, <rkannoth@marvell.com>,
	<gakula@marvell.com>, <sgoutham@marvell.com>
Subject: [PATCH net 0/3] octeontx2: Misc fixes for RVU drivers
Date: Wed, 29 Jul 2026 12:53:34 +0530	[thread overview]
Message-ID: <20260729072337.664479-1-subratp@marvell.com> (raw)

A few independent fixes for the Marvell OcteonTX2 (RVU AF/PF) drivers:

 - Fix a potential buffer overrun by replacing the unbounded sprintf()
   for the "mcs%d" debugfs name with snprintf().
 - Fix aura/CQ BPID assignment under CONFIG_DCB, which assumed
   queue_to_pfc_map was always allocated (not true for SDP VFs).
 - Fix the SC resource cleanup loop that iterated over secy.max
   instead of sc.max.

Baha Mesleh (1):
  octeontx2-af: mcs: Fix SC resource cleanup loop

Geetha sowjanya (1):
  octeontx2-pf: Fix aura BPID assignment when CONFIG_DCB is enabled

Stefan Wiehler (1):
  octeontx2-af: Fix mcs string buffer size

 drivers/net/ethernet/marvell/octeontx2/af/mcs.c     |  2 +-
 .../net/ethernet/marvell/octeontx2/af/rvu_debugfs.c |  4 ++--
 drivers/net/ethernet/marvell/octeontx2/nic/cn20k.c  |  8 +++++---
 .../ethernet/marvell/octeontx2/nic/otx2_common.c    | 13 +++++++------
 4 files changed, 15 insertions(+), 12 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-07-29  7:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29  7:23 Subrat Pandey [this message]
2026-07-29  7:23 ` [PATCH net 1/3] octeontx2-af: Fix mcs string buffer size Subrat Pandey
2026-07-29 10:47   ` Jagielski, Jedrzej
2026-07-29  7:23 ` [PATCH net 2/3] octeontx2-pf: Fix aura BPID assignment when CONFIG_DCB is enabled Subrat Pandey
2026-07-29  7:23 ` [PATCH net 3/3] octeontx2-af: mcs: Fix SC resource cleanup loop Subrat Pandey

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=20260729072337.664479-1-subratp@marvell.com \
    --to=subratp@marvell.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gakula@marvell.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rkannoth@marvell.com \
    --cc=sbhatta@marvell.com \
    --cc=sgoutham@marvell.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