Linux USB
 help / color / mirror / Atom feed
From: Peter Chen <peter.chen@kernel.org>
To: Xu Yang <xu.yang_2@nxp.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Jun Li <jun.li@nxp.com>, dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [EXT] Re: [PATCH] usb: chipidea: udc: check request status before setting device address
Date: Sat, 9 Jul 2022 18:00:19 +0800	[thread overview]
Message-ID: <20220709100019.GA1517786@Peter> (raw)
In-Reply-To: <PAXPR04MB8784CA907581DCFDCFD196128CBE9@PAXPR04MB8784.eurprd04.prod.outlook.com>

On 22-07-04 01:59:45, Xu Yang wrote:
> Hi Peter,
> 
> > -----Original Message-----
> > From: Peter Chen <peter.chen@kernel.org>
> > Sent: Sunday, July 3, 2022 8:42 AM
> > To: Xu Yang <xu.yang_2@nxp.com>
> > Cc: gregkh@linuxfoundation.org; linux-usb@vger.kernel.org; Jun Li
> > <jun.li@nxp.com>; dl-linux-imx <linux-imx@nxp.com>
> > Subject: [EXT] Re: [PATCH] usb: chipidea: udc: check request status before
> > setting device address
> > 
> > Caution: EXT Email
> > 
> > On 22-06-23 11:02:42, Xu Yang wrote:
> > > The complete() function may be called even though request is not
> > > completed.
> > 
> > Would you please explain more when the complete() is called but the
> > request has not completed, and this happens before set_address has
> > finished?
> 
> The following sequence will be a case:
> 1. the HOST sent SET_ADDRESS control message to DEVICE.
> 2. the DEVICE acked this message and queued a usb_request (0 data length) for future IN transfer.
> 3. somehow the setup interrupt is not cleared by USB controller


You mean even software clear the OP_ENDPTSETUPSTAT bits, but controller
itself doesn't clear its interrupt, and trigger the same
interrupt handler again?

> or received other setup token rather IN token.
That's possible. Have you found that at bus analyzer?


> 4. the driver will go through below functions:
> 
> isr_setup_packet_handler(ci);
>   _ep_nuke(ci->ep0in);
>     usb_gadget_giveback_request(&hwep->ep, &hwreq->req);
>       req->complete(ep, req);
>         isr_setup_status_complete();
>           hw_usb_set_address(ci, ci->address);
>             usb_gadget_set_state(&ci->gadget, USB_STATE_ADDRESS);
> 

Would you please add your above description and send patch again?

Peter
> Xu Yang
> 
> > 
> > Peter
> > 
> > > In this case, it's necessary to check request status so as not to set
> > > device address wrongly.
> > >
> > > Fixes: 10775eb17bee ("usb: chipidea: udc: update gadget states
> > > according to ch9")
> > > cc: <stable@vger.kernel.org>
> > > Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
> > > ---
> > >  drivers/usb/chipidea/udc.c | 3 +++
> > >  1 file changed, 3 insertions(+)
> > >
> > > diff --git a/drivers/usb/chipidea/udc.c b/drivers/usb/chipidea/udc.c
> > > index 0c9ae9768a67..8c3e3a635ac2 100644
> > > --- a/drivers/usb/chipidea/udc.c
> > > +++ b/drivers/usb/chipidea/udc.c
> > > @@ -1048,6 +1048,9 @@ isr_setup_status_complete(struct usb_ep *ep,
> > struct usb_request *req)
> > >       struct ci_hdrc *ci = req->context;
> > >       unsigned long flags;
> > >
> > > +     if (req->status < 0)
> > > +             return;
> > > +
> > >       if (ci->setaddr) {
> > >               hw_usb_set_address(ci, ci->address);
> > >               ci->setaddr = false;
> > > --
> > > 2.25.1
> > >
> > 
> > --
> > 
> > Thanks,
> > Peter Chen
> 

-- 

Thanks,
Peter Chen


  reply	other threads:[~2022-07-09 10:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23  3:02 [PATCH] usb: chipidea: udc: check request status before setting device address Xu Yang
2022-07-03  0:42 ` Peter Chen
2022-07-04  1:59   ` [EXT] " Xu Yang
2022-07-09 10:00     ` Peter Chen [this message]
2022-07-11  1:36       ` Xu Yang
2022-07-12  1:22         ` Peter Chen

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=20220709100019.GA1517786@Peter \
    --to=peter.chen@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jun.li@nxp.com \
    --cc=linux-imx@nxp.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=xu.yang_2@nxp.com \
    /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