From: James Lee <james@codeconstruct.com.au>
To: netdev-bot+sashiko@kernel.org
Cc: jk@codeconstruct.com.au, matt@codeconstruct.com.au,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, kees@kernel.org,
gustavoars@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH net-next v2 2/7] net: mctp: usblib: Add test for splits inside headers
Date: Wed, 14 Oct 2026 12:38:52 +0800 [thread overview]
Message-ID: <286884581dfff68a20b6439ca1cbf55fe1ccd6e4.camel@codeconstruct.com.au> (raw)
In-Reply-To: <178893260008.219967.13546498074867789571@kernel.org>
> [Severity: Low]
>
> Should the return value of mctp_usblib_test_rx_complete() be checked
> here,
> as the other call sites in this file do?
Yes, good catch.
> [Severity: High]
>
> Does this leak the skb data buffer? kfree() releases only the struct
> sk_buff itself and skips skb_release_all()/skb_free_head(), so skb->head is
> never freed.
Yes it does, will fix.
> [Severity: Low]
>
> This isn't a bug, but i is never used once the invocations are unrolled, so
> this emits a -Wunused-variable warning and fails the build under
> CONFIG_WERROR with CONFIG_MCTP_TRANSPORT_USBLIB_TEST enabled. The
> declaration is removed again by the next patch in the series, "net: mctp:
> usblib: Add tests of invalid headers", so the final state of the series is
> clean; could it be dropped in this patch instead to keep the series
> bisectable?
Will remove.
next prev parent reply other threads:[~2026-10-14 4:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 2:42 [PATCH net-next v2 0/7] net: mctp: usblib: Increase coverage of kunit testing James Lee
2026-09-03 2:42 ` [PATCH net-next v2 1/7] net: mctp: usblib: Add to parameterized kunit tests James Lee
2026-09-09 5:43 ` netdev-bot+sashiko
2026-09-03 2:42 ` [PATCH net-next v2 2/7] net: mctp: usblib: Add test for splits inside headers James Lee
2026-09-09 5:43 ` netdev-bot+sashiko
2026-10-14 4:38 ` James Lee [this message]
2026-09-09 7:12 ` Simon Horman
2026-09-14 3:14 ` James Lee
2026-09-03 2:42 ` [PATCH net-next v2 3/7] net: mctp: usblib: Add tests of invalid headers James Lee
2026-09-09 5:43 ` netdev-bot+sashiko
2026-09-03 2:42 ` [PATCH net-next v2 4/7] net: mctp: usblib: Complete rx tests James Lee
2026-09-09 5:43 ` netdev-bot+sashiko
2026-09-03 2:42 ` [PATCH net-next v2 5/7] net: mctp: usblib: Simplify allocation logic in mctp_usblib_test_rx_init James Lee
2026-09-03 2:42 ` [PATCH net-next v2 6/7] net: mctp: usblib: Add initial kunit tx tests James Lee
2026-09-09 5:43 ` netdev-bot+sashiko
2026-10-14 4:25 ` James Lee
2026-09-03 2:42 ` [PATCH net-next v2 7/7] net: mctp: usblib: Add test for failing append James Lee
2026-09-09 5:43 ` netdev-bot+sashiko
2026-10-13 9:06 ` James Lee
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=286884581dfff68a20b6439ca1cbf55fe1ccd6e4.camel@codeconstruct.com.au \
--to=james@codeconstruct.com.au \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gustavoars@kernel.org \
--cc=jk@codeconstruct.com.au \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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