From: Claudiu Beznea <claudiu.beznea@tuxon.dev>
To: pavel@nabladev.com, Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
Cc: stable@vger.kernel.org, gregkh@linuxfoundation.org,
cip-dev@lists.cip-project.org,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [cip-dev] [PATCH for 5.10.y] phy: renesas: rcar-gen3-usb2: Fix the use of msleep during spinlock
Date: Tue, 5 May 2026 11:40:18 +0300 [thread overview]
Message-ID: <31002e6e-3983-4e30-aef6-bd2cd51aec40@tuxon.dev> (raw)
In-Reply-To: <afhkX2Ys2BG1gnqy@duo.ucw.cz>
Hi, all,
On 5/4/26 12:18, Pavel Machek via lists.cip-project.org wrote:
> Hi!
>
>> From: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
>>
>> This fixes an issue caused by the use of msleep during spinlock.
>> In the original commit, msleep was changed to mdelay, but this fix was not
>> carried over during the backport to 5.10.y tree.
>
> Doing this as a quick fix is probably okay, but this should not be
> final version.
>
> You are right that msleep inside spinlock will blow up immediately:
>
>> ```
>> [ 62.677594] BUG: scheduling while atomic: kworker/1:2/126/0x00000002
>> [ 62.683957] Modules linked in:
>
> But mdelay for 20 msec inside irqsave spinlock is borderline
> unacceptable, too.
>
> I believe we'll need Renesas to analyze/fix this properly after the
> CVE emergency is done.
>
> This fix is good for now, but better fix is needed.
>
> Claudiu, are you right person for this, or should we cc someone else?
I'm going to investigate and come with a better approach for this.
Thank you and apologies for any inconveniences,
Claudiu
next prev parent reply other threads:[~2026-05-05 8:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 22:58 [PATCH for 5.10.y] phy: renesas: rcar-gen3-usb2: Fix the use of msleep during spinlock Nobuhiro Iwamatsu
2026-05-04 9:18 ` [cip-dev] " Pavel Machek
2026-05-04 11:13 ` Nobuhiro Iwamatsu
2026-05-05 8:40 ` Claudiu Beznea [this message]
2026-05-05 8:49 ` Claudiu Beznea
2026-05-05 8:53 ` Greg KH
2026-05-05 21:01 ` Pavel Machek
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=31002e6e-3983-4e30-aef6-bd2cd51aec40@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=cip-dev@lists.cip-project.org \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=gregkh@linuxfoundation.org \
--cc=iwamatsu@nigauri.org \
--cc=pavel@nabladev.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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