From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: jiale yao <19888972804@163.com>
Cc: Manivannan Sadhasivam <mani@kernel.org>,
Jeff Hugo <jeff.hugo@oss.qualcomm.com>,
Alex Elder <elder@kernel.org>,
mhi@lists.linux.dev, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH] bus: mhi: ep: cancel reset work during controller teardown
Date: Sun, 18 Oct 2026 13:53:12 +0200 [thread overview]
Message-ID: <2026101845-slideshow-entomb-74ad@gregkh> (raw)
In-Reply-To: <74679635.183c.1a14eb6b4b9.Coremail.19888972804@163.com>
On Sun, Oct 18, 2026 at 07:12:39PM +0800, jiale yao wrote:
> At 2026-10-18 14:34:06, "Greg Kroah-Hartman" <gregkh@linuxfoundation.org> wrote:
> >On Sun, Oct 18, 2026 at 12:06:14PM +0800, Jiale Yao wrote:
> >> The doorbell IRQ schedules reset_work on the system workqueue when the
> >> host requests an MHI reset. The controller teardown only drains the
> >> private MHI workqueue before releasing the controller state, so
> >> reset_work can still run after that state has been freed.
> >>
> >> Cancel reset_work before destroying the private workqueue and releasing
> >> the controller resources. The caller is required to power down the
> >> controller first, so the IRQ can no longer queue the work at this point.
> >>
> >> Fixes: 7a97b6b47353 ("bus: mhi: ep: Add support for handling MHI_RESET")
> >> Signed-off-by: Jiale Yao <yaojiale02@163.com>
> >> ---
> >> drivers/bus/mhi/ep/main.c | 1 +
> >> 1 file changed, 1 insertion(+)
> >
> >How was this found and tested? What about a cc: stable?
>
> cc:stable is necessory. The bug was found by my static analysis tools.
Then as per our documentation you need to state that, right?
prev parent reply other threads:[~2026-10-18 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 4:06 [PATCH] bus: mhi: ep: cancel reset work during controller teardown Jiale Yao
2026-10-18 6:34 ` Greg Kroah-Hartman
2026-10-18 11:12 ` jiale yao
2026-10-18 11:14 ` jiale yao
2026-10-18 11:53 ` Greg Kroah-Hartman [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=2026101845-slideshow-entomb-74ad@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=19888972804@163.com \
--cc=elder@kernel.org \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mhi@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.