Re: [PATCH] [rtl8723bs] Remove unnecessary atomic operations for continual_io_error

[Dan Carpenter <dan.carpenter@linaro.org>]

On Tue, Jan 20, 2026 at 09:39:37PM +0800, 2023060904@ycu.edu.cn wrote:
> Hi Dan,
> 
> Thank you for the detailed feedback! I'll address each point below:
> 
> 
> > So you're saying that sd_read32() can only be called by one thread at a
> > time.  What sort of locking enforces this?  I don't see any at first
> > glance, but I also don't want to invest a lot of time into looking for
> > it.  Please explain it clearly in the commit message so reviewers can
> > easily check.
> 
> The single-thread guarantee for SDIO IO functions (sd_read32/sd_write8) comes from two key aspects:
> 1. **Linux kernel driver isolation mechanism**: In the Linux kernel, each SDIO device (e.g., the rtl8723bs wireless card) corresponds to an independent driver instance, and the kernel's device model inherently isolates IO requests for different devices. For a single SDIO device, the kernel serializes all IO requests to it — meaning only one IO operation can be processed for the rtl8723bs card at any time, no concurrent requests exist.

The AI is saying obvious stuff here.  Reviewers are supposed to be
familiar with kernel basics.  It's a waste of time to show reviewers
this paragraph.

> 2. **Driver code logic**: Within the rtl8723bs driver, the sd_read32()/sd_write8() functions are only invoked by the driver's dedicated "IO processing thread". The entire IO execution flow is linear: the driver receives an IO request → processes it via sd_read32()/sd_write8() → completes the request before handling the next one. There is no multi-threaded branching that could call these functions concurrently, so race conditions are impossible.
> 

The AI is spouting nonsense.  Which function is the "driver's dedicated
IO processing thread"?

regards,
dan carpenter