From: Greg KH <gregkh@linuxfoundation.org>
To: Minu Jin <s9430939@naver.com>
Cc: andriy.shevchenko@linux.intel.com, abrahamadekunle50@gmail.com,
milospuric856@gmail.com, zxcv2569763104@gmail.com,
dan.carpenter@linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] staging: rtl8723bs: fix unchecked return value of skb_copy_bits
Date: Wed, 21 Jan 2026 06:05:22 +0100 [thread overview]
Message-ID: <2026012102-thinness-neurotic-6e1b@gregkh> (raw)
In-Reply-To: <20260121023312.2264431-1-s9430939@naver.com>
On Wed, Jan 21, 2026 at 11:33:12AM +0900, Minu Jin wrote:
> The function _rtw_pktfile_read() incorrectly updated the file pointer
> even when skb_copy_bits() failed.
>
> This patch fixes the issue by:
>
> 1. Propagating the negative error code from skb_copy_bits() if
> it fails, preventing internal pointer updates.
>
> 2. Updating all callers (including set_qos) to check the return value
> and handle errors appropriately.
>
> Signed-off-by: Minu Jin <s9430939@naver.com>
> ---
> Changes in v4:
> - Modify _rtw_pktfile_read() to return -EINVAL if the remaining data
> is less than the requested length (suggested by Greg KH).
You do a lot more than just that in that function change.
This needs to be a patch series, each only doing one logical thing.
Please break it up into multiple changes, because as-is, this is hard to
review and verify it is correct.
Also, have you tested this on real hardware?
> -uint _rtw_pktfile_read(struct pkt_file *pfile, u8 *rmem, uint rlen)
> +int _rtw_pktfile_read(struct pkt_file *pfile, u8 *rmem, unsigned int rlen)
> {
> - uint len = 0;
> + int ret;
>
> - len = rtw_remainder_len(pfile);
> - len = (rlen > len) ? len : rlen;
> + if (rtw_remainder_len(pfile) < rlen)
> + return -EINVAL;
Why change the logic here? Are you sure it is correct? Why not
document that in the changelog?
thanks,
greg k-h
prev parent reply other threads:[~2026-01-21 5:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 2:33 [PATCH v4] staging: rtl8723bs: fix unchecked return value of skb_copy_bits Minu Jin
2026-01-21 5:05 ` Greg KH [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=2026012102-thinness-neurotic-6e1b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=abrahamadekunle50@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=milospuric856@gmail.com \
--cc=s9430939@naver.com \
--cc=zxcv2569763104@gmail.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