From: Johan Hovold <johan@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>, Ulf Hansson <ulfh@kernel.org>
Cc: Jakov Novak <jakovnovak30@gmail.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev,
Guangshuo Li <lgs201920130244@gmail.com>,
Runyu Xiao <runyu.xiao@seu.edu.cn>,
Shuah Khan <skhan@linuxfoundation.org>,
syzbot+1ee4f3b9228e35f14677@syzkaller.appspotmail.com,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: Re: [PATCH] mmc: vub300: fix sleeping function call from invalid context in vub300_inactivity_timer_expired
Date: Wed, 9 Sep 2026 08:57:51 +0200 [thread overview]
Message-ID: <aqEDb0THnCM-Q_Vy@hovoldconsulting.com> (raw)
In-Reply-To: <CAMuHMdX6JfqpLMGDQJSQ8E8XNobRwr16LOzuphPt3Afs-OZdJA@mail.gmail.com>
On Mon, Sep 07, 2026 at 04:48:00PM +0200, Geert Uytterhoeven wrote:
> Hi Johan,
>
> On Mon, 7 Sept 2026 at 15:55, Johan Hovold <johan@kernel.org> wrote:
> > On Mon, Sep 07, 2026 at 02:17:45PM +0200, Geert Uytterhoeven wrote:
> > > On Mon, 17 Aug 2026 at 10:13, Johan Hovold <johan@kernel.org> wrote:
> > > > On Sun, Aug 16, 2026 at 05:38:09PM +0200, Jakov Novak wrote:
> > > > > Currently, the function vub300_inactivity_timer_expired, which gets
> > > > > called in a softirq context, calls a sleeping function in the following
> > > > > call chain:
> > > > >
> > > > > vub300_inactivity_timer_expired -> kref_put -> vub300_delete ->
> > > > > mmc_free_host -> cancel_delayed_work_sync -> __cancel_work_sync ->
> > > > > might_sleep -> BUG
> > > > >
> > > > > Fix this by replacing kref_put(&vub300->kref, vub300_delete) with
> > > > > vub300_queue_dead_work(vub300), which does the same thing, but in a
> > > > > workqueue context.
> > > > >
> > > > > Fixes: 88095e7b473a ("mmc: Add new VUB300 USB-to-SD/SDIO/MMC driver")
> > > >
> > > > This isn't the commit that introduced the issue. The blocking call in
> > > > mmc_free_host() was added by commit 1036f69e2513 ("mmc: core: Cancel
> > > > delayed work before releasing host") in 2023.
> > > >
> > > > I didn't look at this in any detail, but having that call in
> > > > mmc_free_host() (e.g. rather than in mmc_remove_host()) looks wrong so
> > > > perhaps the fix really lies in MMC core.
> > >
> > > mmc_remove_host() can only be called after a sucessful probe, while
> > > commit 1036f69e2513 fixed an issue where the last probe step failed
> > > with -EPROBE_DEFER.
> >
> > Sure, but should you be scheduling rescan work before all resources have
> > been set up and the host has been registered?
>
> I would like to defer that question to the TMIO experts.
Are they on CC?
Ulf, perhaps you can take a look at this? It seems wrong to enable
interrupts and trigger rescans before the host controller has been set
up and registered.
Johan
next prev parent reply other threads:[~2026-09-09 6:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 15:38 [PATCH] mmc: vub300: fix sleeping function call from invalid context in vub300_inactivity_timer_expired Jakov Novak
2026-08-17 8:13 ` Johan Hovold
2026-08-30 9:32 ` Tetsuo Handa
2026-09-07 11:16 ` Jakov Novak
2026-09-07 12:19 ` Geert Uytterhoeven
2026-09-07 12:17 ` Geert Uytterhoeven
2026-09-07 13:55 ` Johan Hovold
2026-09-07 14:48 ` Geert Uytterhoeven
2026-09-09 6:57 ` Johan Hovold [this message]
2026-09-09 7:38 ` Geert Uytterhoeven
2026-09-09 8:02 ` Johan Hovold
2026-09-09 17:24 ` Wolfram Sang
2026-09-11 7:04 ` Johan Hovold
2026-09-11 11:14 ` Jakov Novak
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=aqEDb0THnCM-Q_Vy@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=geert@linux-m68k.org \
--cc=jakovnovak30@gmail.com \
--cc=lgs201920130244@gmail.com \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=runyu.xiao@seu.edu.cn \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+1ee4f3b9228e35f14677@syzkaller.appspotmail.com \
--cc=ulfh@kernel.org \
--cc=wsa+renesas@sang-engineering.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 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.