Re: [PATCH] wifi: wcn36xx: drop the SMSM state references on probe error

[Krzysztof Kozlowski]

On Tue, 03 Nov 2026 10:29:02 +0000, Wentao Liang wrote:
> wcn36xx_platform_get_resources() acquires two SMSM state handles with
> qcom_smem_state_get(). Each successful call returns a reference that the
> caller has to release with qcom_smem_state_put(), which is only done by
> wcn36xx_remove() for a device that probed successfully.
> 
> Several error paths in between return without dropping the references
> already taken: failing to get the "tx-rings-empty" handle leaks the
> "tx-enable" one, and failing to look up the qcom,mmio phandle or to map
> one of the mmio regions leaks both of them. A probe that fails after the
> first successful acquisition therefore leaks the SMSM state references
> for good.
> 
> Make these paths unwind through the existing label chain and put the
> handles there.
> 
> Fixes: f303a9311065 ("wcn36xx: Transition driver to SMD client")
> Cc: stable@xxxxxxxxxxxxxxx
> Assisted-by: DeepSeek-V4.1-Flash and OpenAI Codex
> Signed-off-by: Wentao Liang <vulab@xxxxxxxxxxx>
> ---
>  drivers/net/wireless/ath/wcn36xx/main.c | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
> 



Multiple things here:
1. Your team ignored completely previous feedback. Multiple times.

2. You use multiple identities with this email address, thus I doubt that we
   speak with an actual person.

3. Your bot does not even bother running checkpatch, right?

4. Nothing of this was reproduced nor tested.

5. Finally, the same feedback:
You sent multiple independent patches, to multiple independent
subsystems. The amount of these patches clearly suggest this was
AI generated and most likely not tested.

More importantly, you sent all this work without properly organizing
relevant patches into patchsets. This makes reviewing difficult
and might cause multiple reviewers to address the same issue.
Replying to the entire set is impossible and requires handling each
patch independently, instead of applying or discarding the set.
Maintainers also won't see the bigger picture of your work. Quite
worrying.

This is on the verge of hostile patch: bomb us with so many
contributions, we won't be able to handle them in efficient manner,
like responding ONCE to ask you to slow down.  Considering all this
is untested and LLM generated, I have even more doubts whether this
should be considered for review.

Please read kernel documentation BEFORE posting more work. It will
explain you how to identify subsystems, how to organize your work per
subsystem (so a patchset grouping multiple patches with a short cover
letter), how to document the issue discovery method and what was
or was not tested.

Best regards,
Krzysztof