public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH RESEND] usb: renesas_usbhs: Add error handling for usbhsf_fifo_select()
Date: Fri, 25 Apr 2025 13:01:21 +0200	[thread overview]
Message-ID: <2025042552-upper-clatter-0d9d@gregkh> (raw)
In-Reply-To: <20250422023825.2016-1-vulab@iscas.ac.cn>

On Tue, Apr 22, 2025 at 10:38:24AM +0800, Wentao Liang wrote:
> In usbhsf_dcp_data_stage_prepare_pop(), the return value of
> usbhsf_fifo_select() needs to be checked. A proper implementation
> can be found in usbhsf_dma_try_pop_with_rx_irq().
> 
> Add an error check and jump to PIO pop when FIFO selection fails.
> 
> Fixes: 9e74d601de8a ("usb: gadget: renesas_usbhs: add data/status stage handler")
> Cc: stable@vger.kernel.org # v3.2+
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
> ---
>  drivers/usb/renesas_usbhs/fifo.c | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/usb/renesas_usbhs/fifo.c b/drivers/usb/renesas_usbhs/fifo.c
> index 10607e273879..6cc07ab4782d 100644
> --- a/drivers/usb/renesas_usbhs/fifo.c
> +++ b/drivers/usb/renesas_usbhs/fifo.c
> @@ -466,6 +466,7 @@ static int usbhsf_dcp_data_stage_prepare_pop(struct usbhs_pkt *pkt,
>  	struct usbhs_pipe *pipe = pkt->pipe;
>  	struct usbhs_priv *priv = usbhs_pipe_to_priv(pipe);
>  	struct usbhs_fifo *fifo = usbhsf_get_cfifo(priv);
> +	int ret;
>  
>  	if (usbhs_pipe_is_busy(pipe))
>  		return 0;
> @@ -480,10 +481,14 @@ static int usbhsf_dcp_data_stage_prepare_pop(struct usbhs_pkt *pkt,
>  
>  	usbhs_pipe_sequence_data1(pipe); /* DATA1 */
>  
> -	usbhsf_fifo_select(pipe, fifo, 0);
> +	ret = usbhsf_fifo_select(pipe, fifo, 0);
> +	if (ret < 0)
> +		goto usbhsf_pio_prepare_pop;
> +
>  	usbhsf_fifo_clear(pipe, fifo);
>  	usbhsf_fifo_unselect(pipe, fifo);
>  
> +usbhsf_pio_prepare_pop:
>  	/*
>  	 * change handler to PIO pop
>  	 */
> -- 
> 2.42.0.windows.2

How was this tested?  I still think this is wrong, as the cleanup does
not look correct.

thanks,

greg k-h

  reply	other threads:[~2025-04-25 11:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22  2:38 [PATCH RESEND] usb: renesas_usbhs: Add error handling for usbhsf_fifo_select() Wentao Liang
2025-04-25 11:01 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-14  7:25 Wentao Liang
2025-04-14  7:38 ` Greg KH

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=2025042552-upper-clatter-0d9d@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=vulab@iscas.ac.cn \
    /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