From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mta1.migadu.com (out-33.mta1.migadu.com [95.215.58.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E95C24B1D1A for ; Tue, 13 Oct 2026 07:10:25 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.33 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791875427; cv=none; b=qMsbMVnXanfKocE0FLBohzhgmPHoY3uIJBiolZyBJjbGxQ4PlC6PFPEl2SYc3I7UpmJMaNqc/IFzldQ8TuAw5So6N6s0siQnjI4E7X0rT+7ySzj8DPhJRKIV34da0lq3BlVCJ5vadh7mY42ILT0czn9G9LoZJxQdXI1cKEuvpoc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791875427; c=relaxed/simple; bh=yw7AoW/HGY0hyzkfaYvMgbzeBdxHTR8bh7HvAFdSAg4=; h=Mime-Version:Content-Type:Date:Message-Id:Cc:Subject:From:To: References:In-Reply-To; b=hDbv+5bGmSdwR9BwbidBGjJHOzb/siPmcIswEmFzzo7USayAxDvmBGf3pi51Ww0fi0fWjCAiNTRHZ0y4V7lQzOzNinxu1NAOof8EkN1dAttH4QPNlM4+i5JJY+h3Agy0Fnl7bADyyBE3xbadKRlu0VcmDqMCNVn9AgRmJRlpV54= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=PCZ0gp8E; arc=none smtp.client-ip=95.215.58.33 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="PCZ0gp8E" X-Envelope-To: stable@vger.kernel.org DKIM-Signature: a=rsa-sha256; bh=yw7AoW/HGY0hyzkfaYvMgbzeBdxHTR8bh7HvAFdSAg4=; c=simple/simple; d=linux.dev; h=from:to:subject:date:message-id:mime-version:content-type; s=key1; t=1791875424; v=1; x=1792480224; b=PCZ0gp8EUgRwnwgb8Ix7uFS/fUJrFWeVppyjlLHnm9G7CAjPVAokvPae4PoD0bJVOP5q/d4R EOK0af+Lnc99TqqaWDyOugjob/3nMvCgvZaxY30Y54ERVyy0uufVy5hEmf1bRPYXvzysNouhExr /nf+dgavd8rqoc+WR2FOmlDk= X-Envelope-To: stable@vger.kernel.org Received: by smtp.migadu.com with ESMTPS id 34e6b5eb821ee27c; Tue, 13 Oct 2026 07:10:21 +0000 X-Mizu-Trace-ID: 34e6b5eb821ee27c X-Migadu-Flow: FLOW_OUT Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Tue, 13 Oct 2026 07:10:20 +0000 Message-Id: Cc: "Luka Gejak" , "Martin Blumenstingl" , "Jernej Skrabec" , "Ulf Hansson" , , Subject: Re: [PATCH rtw-next v5 1/4] wifi: rtw88: sdio: Handle allocation and read errors in rtw_sdio_rxfifo_recv From: "Luka Gejak" To: "Alastair D'Silva" , , "Ping-Ke Shih" , "Kalle Valo" X-Mailer: aerc 0.22.0 References: <20261011220755.1673367-1-alastair@d-silva.org> <20261011220755.1673367-2-alastair@d-silva.org> In-Reply-To: <20261011220755.1673367-2-alastair@d-silva.org> On Sun Oct 11, 2026 at 10:07 PM UTC, Alastair D'Silva wrote: > When dev_alloc_skb() or rtw_sdio_read_port() fails, rtw_sdio_rxfifo_recv(= ) > returns without reading data. Because it returned void, the caller still > counted rx_len against the loop budget while leaving data stranded in the > FIFO. > > Return an error code from rtw_sdio_rxfifo_recv() on failure and break out > of the receive loop in the caller immediately. > > Fixes: 65371a3f14e7 ("wifi: rtw88: sdio: Add HCI implementation for SDIO = based chipsets") > Cc: stable@vger.kernel.org > Assisted-by: LLM > Acked-by: Ping-Ke Shih > Signed-off-by: Alastair D'Silva > --- Reviewed-by: Luka Gejak Best regards, Luka Gejak