From: Greg KH <gregkh@linuxfoundation.org>
To: Claudiu Beznea <claudiu.beznea@tuxon.dev>
Cc: pavel@nabladev.com, Nobuhiro Iwamatsu <iwamatsu@nigauri.org>,
stable@vger.kernel.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 10:53:25 +0200 [thread overview]
Message-ID: <2026050519-stencil-sequester-187b@gregkh> (raw)
In-Reply-To: <f81033c2-3432-4275-b5a7-78c61c31502a@tuxon.dev>
On Tue, May 05, 2026 at 11:49:24AM +0300, Claudiu Beznea wrote:
>
>
> On 5/5/26 11:40, Claudiu Beznea wrote:
> > 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.
>
> On a second thought, the proper fix would have to go to upstream first. To
> fix the problem currently seen, could we integrate this patch as is?
No, please work upstream first.
next prev parent reply other threads:[~2026-05-05 8:53 UTC|newest]
Thread overview: 9+ 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
2026-05-05 8:49 ` Claudiu Beznea
2026-05-05 8:53 ` Greg KH [this message]
2026-05-05 21:01 ` Pavel Machek
2026-06-02 18:21 ` [PATCH] " Sasha Levin
2026-06-03 20:22 ` 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=2026050519-stencil-sequester-187b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cip-dev@lists.cip-project.org \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=claudiu.beznea@tuxon.dev \
--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 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.