From: Thorsten Leemhuis <linux@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: bug: usb: gadget: FSL_UDC_CORE Corrupted request list leads to unrecoverable loop.
Date: Mon, 1 Nov 2021 17:42:30 +0100 [thread overview]
Message-ID: <7ee1c6ac-a75a-06bc-f6e5-6aa529919f0c@leemhuis.info> (raw)
In-Reply-To: <MWHPR2201MB152074F47BF142189365627B91879@MWHPR2201MB1520.namprd22.prod.outlook.com>
On 29.10.21 19:14, Eugene Bordenkircher wrote:
> Hello all,
>
> We've discovered a situation where the FSL udc driver
> (drivers/usb/gadget/udc/fsl_udc_core.c) will enter a loop iterating
> over the request queue, but the queue has been corrupted at some
> point so it loops infinitely. I believe we have narrowed into the
> offending code, but we are in need of assistance trying to find an
> appropriate fix for the problem. The identified code appears to be
> in all versions of the Linux kernel the driver exists in.
#regzbot ^introduced f79a60b8785
#regzbot link:
https://lore.kernel.org/all/CADRPPNSrhiwr8jmBb2h4cFYqHtuDKK8rL0i6Bkg7+xEyXJPATA@mail.gmail.com/
#regzbot link:
https://lore.kernel.org/all/2c275adc278477e1e512ea6ecc0c1f4dcc46969d.camel@infinera.com/
prev parent reply other threads:[~2021-11-01 16:42 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 17:14 bug: usb: gadget: FSL_UDC_CORE Corrupted request list leads to unrecoverable loop Eugene Bordenkircher
2021-10-29 17:14 ` Eugene Bordenkircher
2021-10-29 17:24 ` Eugene Bordenkircher
2021-10-29 17:24 ` Eugene Bordenkircher
2021-10-29 23:14 ` Li Yang
2021-10-29 23:14 ` Li Yang
2021-10-30 14:20 ` Joakim Tjernlund
2021-10-30 14:20 ` Joakim Tjernlund
2021-11-02 21:15 ` Joakim Tjernlund
2021-11-02 21:15 ` Joakim Tjernlund
2021-11-15 8:36 ` Thorsten Leemhuis
2021-11-15 8:36 ` Thorsten Leemhuis
2021-11-16 19:11 ` Eugene Bordenkircher
2021-11-16 19:11 ` Eugene Bordenkircher
2021-11-25 13:59 ` Thorsten Leemhuis
2021-11-25 13:59 ` Thorsten Leemhuis
2021-11-29 17:24 ` Eugene Bordenkircher
2021-11-29 17:24 ` Eugene Bordenkircher
2021-11-29 23:37 ` Leo Li
2021-11-29 23:48 ` Eugene Bordenkircher
2021-11-30 11:56 ` Joakim Tjernlund
2021-12-01 14:19 ` Joakim Tjernlund
2021-12-02 20:35 ` Leo Li
2021-12-02 22:45 ` Joakim Tjernlund
2021-12-04 0:40 ` Leo Li
2022-01-20 12:54 ` Thorsten Leemhuis
2022-02-18 7:11 ` Thorsten Leemhuis
2022-02-18 10:21 ` Joakim Tjernlund
2022-02-18 10:39 ` gregkh
2022-02-18 10:39 ` gregkh
2022-02-18 11:17 ` Joakim Tjernlund
2022-02-18 11:17 ` Joakim Tjernlund
2022-02-18 11:48 ` gregkh
2022-02-18 11:48 ` gregkh
2021-11-01 16:42 ` Thorsten Leemhuis [this message]
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=7ee1c6ac-a75a-06bc-f6e5-6aa529919f0c@leemhuis.info \
--to=linux@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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.