mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: Minu Jin <s9430939@naver.com>, gregkh@linuxfoundation.org
Cc: andriy.shevchenko@linux.intel.com, dan.carpenter@linaro.org,
	abrahamadekunle50@gmail.com, zxcv2569763104@gmail.com,
	milospuric856@gmail.com, karanja99erick@gmail.com,
	weibu@redadmin.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 0/2] staging: rtl8723bs: Fix error handling in _rtw_pktfile_read()
Date: Sun, 24 May 2026 21:30:01 +0300	[thread overview]
Message-ID: <c6828c20-8f77-423e-a744-344d09c54488@gmail.com> (raw)
In-Reply-To: <20260127153811.1592900-1-s9430939@naver.com>

On 27/01/2026 17:38, Minu Jin wrote:
> This series improves error handling in _rtw_pktfile_read() and cleans up
> the code style to comply with kernel standards.
> 
> 1. The first patch combines the logic change and caller updates.
>    The function change and the caller updates must be in the same
>    patch. If they are separated, the code will not work correctly 
>    or will cause errors at that specific point in the history.
> 
> 2. The second patch focuses purely on code style cleanup (changing uint
>    to unsigned int) as requested by Andy Shevchenko.
> 
> Regarding the logic change in _rtw_pktfile_read():
> 
>     The original code used a ternary operator to read whatever data was 
>     available, even if it was less than requested. This could lead to 
>     callers processing incomplete data without knowing it.
> 
>     I have changed this to return -EINVAL when the remaining data is insufficient. 
>     This is safer because most callers expect the exact amount of data and 
>     should not proceed with a partial read.
> 
> Testing and Verification:
> 
>     I do not have access to the physical RTL8723BS hardware. However, I have
>     performed a rigorous manual audit of the data path and verified the
>     changes using Smatch static analysis. The analysis confirmed that no
>     new warnings or logical regressions were introduced in the modified files.
> 

Hi!

I have some bad news:

https://bbs.archlinux.org/viewtopic.php?id=313401

[quote]

Hey everyone,

I recently upgraded my system, and now I’m having a strange issue with my WiFi (Realtek RTL8723BS).

now I can no longer connect to any WiFi networks as a client. however, creating an Access Point (AP) still works fine, but whenever I try to connect to an existing network, the connection fails.

dmesg logs:
Every time I attempt a connection, dmesg gets spammed with this error:

    [ 1083.925640] rtl8723bs mmc0:0001:1 wlan0: xmit_xmitframes: coalesce failed with error -22
    [ 1084.921217] rtl8723bs mmc0:0001:1 wlan0: xmit_xmitframes: coalesce failed with error -22
    [ 1085.921434] rtl8723bs mmc0:0001:1 wlan0: xmit_xmitframes: coalesce failed with error -22
    [ 1086.922320] rtl8723bs mmc0:0001:1 wlan0: xmit_xmitframes: coalesce failed with error -22
    ....

Has anyone encountered this specific "coalesce" error with the rtl8723bs driver? I'm looking for advice on whether this is a known bug in recent kernels or if there's a specific module parameter I should try to bypass this.

System Info:

    Chipset: RTL8723BS (SDIO)

    Kernel version: 7.0.3-zen1-2-zen

update: I fixed the issue after kernel downgrade

[/quote]

  parent reply	other threads:[~2026-05-24 18:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27 15:38 Minu Jin
2026-01-27 15:38 ` [PATCH v8 1/2] staging: rtl8723bs: update _rtw_pktfile_read() to return error codes Minu Jin
2026-01-27 15:38 ` [PATCH v8 2/2] staging: rtl8723bs: clean up _rtw_pktfile_read() Minu Jin
2026-05-24 18:30 ` Bitterblue Smith [this message]
2026-06-03  0:48   ` [PATCH v8 0/2] staging: rtl8723bs: Fix error handling in _rtw_pktfile_read() Andy Shevchenko
2026-06-03 13:40     ` Bitterblue Smith
2026-06-03 14:06       ` Andy Shevchenko
2026-06-04 21:47         ` Bitterblue Smith
2026-06-05  5:53           ` Andy Shevchenko

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=c6828c20-8f77-423e-a744-344d09c54488@gmail.com \
    --to=rtl8821cerfe2@gmail.com \
    --cc=abrahamadekunle50@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dan.carpenter@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=karanja99erick@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=milospuric856@gmail.com \
    --cc=s9430939@naver.com \
    --cc=weibu@redadmin.org \
    --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

all inboxes | Powered by JetHome®