From: "Oscar Alejandro Sánchez Lucero via B4 Relay" <devnull+aleszlucero.gmail.com@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
"Oscar Alejandro Sánchez Lucero" <aleszlucero@gmail.com>
Subject: [PATCH 0/2] staging: octeon: cleanups and safety fixes in ethernet-tx.c
Date: Sat, 07 Nov 2026 05:28:39 -0600 [thread overview]
Message-ID: <20261107-octeon-tx-fixes-v1-0-db03f73a6e6f@gmail.com> (raw)
This series fixes memory safety and API correctness issues found in
drivers/staging/octeon/ethernet-tx.c during static analysis:
1. Fix return types in cvm_oct_xmit_pow() to use NETDEV_TX_OK instead of
naked integer '0', and change pointers to u8 * to avoid non-standard
void pointer arithmetic warnings.
2. Add packet length validation to avoid a buffer overflow when copying
into the FPA packet pool, and bound WQE data memcpys with min_t() to
prevent out-of-bounds reads on short/malformed frames.
Signed-off-by: Oscar Alejandro Sánchez Lucero <aleszlucero@gmail.com>
---
Oscar Alejandro Sánchez Lucero (2):
staging: octeon: fix return type and void arithmetic in cvm_oct_xmit_pow()
staging: octeon: prevent buffer overflow in cvm_oct_xmit_pow()
drivers/staging/octeon/ethernet-tx.c | 34 ++++++++++++++++++++++------------
1 file changed, 22 insertions(+), 12 deletions(-)
---
base-commit: ddfe51b0a0f5dc9e415cc2c8ad8db17532dd426b
change-id: 20261107-octeon-tx-fixes-bf70dea7c3d0
Best regards,
--
Oscar Alejandro Sánchez Lucero <aleszlucero@gmail.com>
next reply other threads:[~2026-11-07 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 11:28 Oscar Alejandro Sánchez Lucero via B4 Relay [this message]
2026-11-07 11:28 ` [PATCH 1/2] staging: octeon: fix return type and void arithmetic in cvm_oct_xmit_pow() Oscar Alejandro Sánchez Lucero via B4 Relay
2026-11-07 11:28 ` [PATCH 2/2] staging: octeon: prevent buffer overflow " Oscar Alejandro Sánchez Lucero via B4 Relay
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=20261107-octeon-tx-fixes-v1-0-db03f73a6e6f@gmail.com \
--to=devnull+aleszlucero.gmail.com@kernel.org \
--cc=aleszlucero@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.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
all inboxes | Powered by JetHome®