From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Guido Kiener <Guido.Kiener@rohde-schwarz.com>
Cc: "qiang.zhang@windriver.com" <qiang.zhang@windriver.com>,
"stern@rowland.harvard.edu" <stern@rowland.harvard.edu>,
"dave penkler (dpenkler@gmail.com)" <dpenkler@gmail.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH v2] USB: usbtmc: Fix RCU stall warning
Date: Tue, 27 Jul 2021 11:12:17 +0200 [thread overview]
Message-ID: <YP/N8cOS8+UaZ8Ag@kroah.com> (raw)
In-Reply-To: <7ad985430b1e4ddcb642001f4dc8be84@rohde-schwarz.com>
On Tue, Jul 27, 2021 at 07:56:27AM +0000, Guido Kiener wrote:
> > > From: Qiang.zhang>
> > > rcu: INFO: rcu_preempt self-detected stall on CPU
> > > rcu: 1-...!: (2 ticks this GP) idle=d92/1/0x4000000000000000
> > > softirq=25390/25392 fqs=3
> > > (t=12164 jiffies g=31645 q=43226)
> > > rcu: rcu_preempt kthread starved for 12162 jiffies! g31645 f0x0
> > > RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=0
> > > rcu: Unless rcu_preempt kthread gets sufficient CPU time,
> > > OOM is now expected behavior.
> > > rcu: RCU grace-period kthread stack dump:
> > > task:rcu_preempt state:R running task
> > > ...........
> > > usbtmc 3-1:0.0: unknown status received: -71 usbtmc 3-1:0.0: unknown
> > > status
> > > received: -71 usbtmc 3-1:0.0: unknown status received: -71 usbtmc 3-1:0.0:
> > > unknown status received: -71 usbtmc 3-1:0.0: unknown status received:
> > > -71 usbtmc
> > > 3-1:0.0: unknown status received: -71 usbtmc 3-1:0.0: unknown status
> > > received: -71 usbtmc 3-1:0.0: unknown status received: -71 usbtmc
> > > 3-1:0.0: usb_submit_urb
> > > failed: -19
> > >
> > > The function usbtmc_interrupt() resubmits urbs when the error status
> > > of an urb is - EPROTO. In systems using the dummy_hcd usb controller
> > > this can result in endless interrupt loops when the usbtmc device is disconnected
> > from the host system.
> > >
> > > Since host controller drivers already try to recover from transmission
> > > errors, there is no need to resubmit the urb or try other solutions to repair the error
> > situation.
> > >
> > > In case of errors the INT pipe just stops to wait for further packets.
> > >
> > > Fixes: dbf3e7f654c0 ("Implement an ioctl to support the USMTMC-USB488
> > > READ_STATUS_BYTE operation")
> > > Cc: stable@vger.kernel.org
> > > Reported-by: syzbot+e2eae5639e7203360018@syzkaller.appspotmail.com
> > > Signed-off-by: Qiang.zhang <qiang.zhang@windriver.com>
> > > ---
> > > v1->v2:
> > > Add fixes and stable tags, modify description information.
> > >
> > > drivers/usb/class/usbtmc.c | 9 +--------
> > > 1 file changed, 1 insertion(+), 8 deletions(-)
> > >
> > > diff --git a/drivers/usb/class/usbtmc.c b/drivers/usb/class/usbtmc.c
> > > index
> > > 74d5a9c5238a..73f419adce61 100644
> > > --- a/drivers/usb/class/usbtmc.c
> > > +++ b/drivers/usb/class/usbtmc.c
> > > @@ -2324,17 +2324,10 @@ static void usbtmc_interrupt(struct urb *urb)
> > > dev_err(dev, "overflow with length %d, actual length is %d\n",
> > > data->iin_wMaxPacketSize, urb->actual_length);
> > > fallthrough;
> > > - case -ECONNRESET:
> > > - case -ENOENT:
> > > - case -ESHUTDOWN:
> > > - case -EILSEQ:
> > > - case -ETIME:
> > > - case -EPIPE:
> > > + default:
> > > /* urb terminated, clean up */
> > > dev_dbg(dev, "urb terminated, status: %d\n", status);
> > > return;
> > > - default:
> > > - dev_err(dev, "unknown status received: %d\n", status);
> > > }
> > > exit:
> > > rv = usb_submit_urb(urb, GFP_ATOMIC);
> > > --
> > > 2.25.1
> >
> > The patch looks good to me and is tested on my machine.
> >
> > Ack-by: Guido Kiener <guido.kiener@rohde-schwarz.com>
> >
> > -Guido
>
> Greg,
>
> Can you please add the patch https://patchwork.kernel.org/project/linux-usb/list/?series=520033
> Dave, Alan, and I are ok with the patch.
Relax, I will get to it :)
next prev parent reply other threads:[~2021-07-27 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 7:56 [PATCH v2] USB: usbtmc: Fix RCU stall warning Guido Kiener
2021-07-27 9:12 ` gregkh [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-23 8:39 Guido Kiener
2021-07-27 13:52 ` gregkh
2021-07-23 0:43 qiang.zhang
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=YP/N8cOS8+UaZ8Ag@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Guido.Kiener@rohde-schwarz.com \
--cc=dpenkler@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=qiang.zhang@windriver.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).