From: "Jakov Novak" <jakovnovak30@gmail.com>
To: "Tetsuo Handa" <penguin-kernel@I-love.SAKURA.ne.jp>,
"Johan Hovold" <johan@kernel.org>,
"Jakov Novak" <jakovnovak30@gmail.com>
Cc: <linux-mmc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-kernel-mentees@lists.linux.dev>,
"Ulf Hansson" <ulfh@kernel.org>,
"Guangshuo Li" <lgs201920130244@gmail.com>,
"Runyu Xiao" <runyu.xiao@seu.edu.cn>,
"Shuah Khan" <skhan@linuxfoundation.org>,
<syzbot+1ee4f3b9228e35f14677@syzkaller.appspotmail.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>
Subject: Re: [PATCH] mmc: vub300: fix sleeping function call from invalid context in vub300_inactivity_timer_expired
Date: Mon, 07 Sep 2026 13:16:59 +0200 [thread overview]
Message-ID: <DL91IWM6YXRN.3892K60CVKZ3U@gmail.com> (raw)
In-Reply-To: <61c4cee5-3c63-4b09-abbf-bf945b538403@I-love.SAKURA.ne.jp>
> syzbot has an AI-generated patch at
> https://lkml.kernel.org/r/49982079-95f4-4e8c-bbbc-bcb127e2f378@mail.kernel.org .
>
> Please check.
I checked the AI-generated patch and it just uses the deadworkqueue in a
new function. That is the same thing I am doing except that I'm using
the vub300_queue_dead_work function instead of writing some new code
that does the same thing.
The real question is whether mmc_free_host should be allowed to invoke
the sleep function or not. Geert needs to elaborate on that since he
added this change in 1036f69e2513 ("mmc: core: Cancel
delayed work before releasing host").
next prev parent reply other threads:[~2026-09-07 11:18 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 [this message]
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
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=DL91IWM6YXRN.3892K60CVKZ3U@gmail.com \
--to=jakovnovak30@gmail.com \
--cc=geert+renesas@glider.be \
--cc=johan@kernel.org \
--cc=lgs201920130244@gmail.com \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=runyu.xiao@seu.edu.cn \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+1ee4f3b9228e35f14677@syzkaller.appspotmail.com \
--cc=ulfh@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.