All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavan Kondeti <pkondeti@codeaurora.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] EHCI: Update qTD next pointer in QH overlay region during unlink
Date: Fri, 07 Sep 2012 21:28:36 +0530	[thread overview]
Message-ID: <504A19AC.8080405@codeaurora.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1209071151130.1674-100000@iolanthe.rowland.org>

On 9/7/2012 9:22 PM, Alan Stern wrote:
> On Fri, 7 Sep 2012, Pavankumar Kondeti wrote:
> 
>> There is a possibility of QH overlay region having reference to a stale
>> qTD pointer during unlink.
>>
>> Consider an endpoint having two pending qTD before unlink process begins.
>> The endpoint's QH queue looks like this.
>>
>> qTD1 --> qTD2 --> Dummy
>>
>> To unlink qTD2, QH is removed from asynchronous list and Asynchronous
>> Advance Doorbell is programmed.  The qTD1's next qTD pointer is set to
>> qTD2'2 next qTD pointer and qTD2 is retired upon controller's doorbell
>> interrupt.  If QH's current qTD pointer points to qTD1, transfer overlay
>> region still have reference to qTD2. But qtD2 is just unlinked and freed.
>> This may cause EHCI system error.  Fix this by updating qTD next pointer
>> in QH overlay region with the qTD next pointer of the current qTD.
>>
>> Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
>> ---
>>  drivers/usb/host/ehci-q.c |   12 ++++++++++--
>>  1 files changed, 10 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/usb/host/ehci-q.c b/drivers/usb/host/ehci-q.c
>> index 9bc39ca..4b66374 100644
>> --- a/drivers/usb/host/ehci-q.c
>> +++ b/drivers/usb/host/ehci-q.c
>> @@ -128,9 +128,17 @@ qh_refresh (struct ehci_hcd *ehci, struct ehci_qh *qh)
>>  	else {
>>  		qtd = list_entry (qh->qtd_list.next,
>>  				struct ehci_qtd, qtd_list);
>> -		/* first qtd may already be partially processed */
>> -		if (cpu_to_hc32(ehci, qtd->qtd_dma) == qh->hw->hw_current)
>> +		/*
>> +		 * first qtd may already be partially processed.
>> +		 * If we come here during unlink, the QH overlay region
>> +		 * might have reference to the just unlinked qtd. The
>> +		 * qtd is updated in qh_completions(). Update the QH
>> +		 * overlay here.
>> +		 */
>> +		if (cpu_to_hc32(ehci, qtd->qtd_dma) == qh->hw->hw_current) {
>> +			qh->hw->hw_qtd_next = qtd->hw_next;
>>  			qtd = NULL;
>> +		}
>>  	}
>>  
>>  	if (qtd)
> 
> Acked-by: Alan Stern <stern@rowland.harvard.edu>
> 

Thanks Alan for reviewing the patch.

> Have you been able to determine that this eliminates your host system
> errors?

Yes. We are able to determine that this patch is fixing the EHCI system
error.

-- 
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation.

  reply	other threads:[~2012-09-07 15:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <504969C9.2070209@codeaurora.org>
2012-09-07  5:53 ` [PATCH] EHCI: Update qTD next pointer in QH overlay region during unlink Pavankumar Kondeti
2012-09-07 15:52   ` Alan Stern
2012-09-07 15:58     ` Pavan Kondeti [this message]
     [not found]     ` <Pine.LNX.4.44L0.1209071151130.1674-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2012-09-07 16:16       ` Alan Stern

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=504A19AC.8080405@codeaurora.org \
    --to=pkondeti@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.