mhi.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: gregkh@linuxfoundation.org
Cc: quic_hemantk@quicinc.com, mhi@lists.linux.dev,
	ath11k@lists.infradead.org, kvalo@kernel.org
Subject: [GIT PULL] MHI fixes for v6.0
Date: Mon, 29 Aug 2022 22:47:46 +0530	[thread overview]
Message-ID: <20220829171746.GA84334@thinkpad> (raw)

The following changes since commit 568035b01cfb107af8d2e4bd2fb9aea22cf5b868:

  Linux 6.0-rc1 (2022-08-14 15:50:18 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mani/mhi.git tags/mhi-fixes-for-v6.0

for you to fetch changes up to acc5495bf764e7e441193f972d96c5d2887f6b8b:

  bus: mhi: host: Fix up null pointer access in mhi_irq_handler (2022-08-29 22:33:46 +0530)

----------------------------------------------------------------
A single fix targeting the MHI host stack:

 - Since the commit 1227d2a20cd7 ("bus: mhi: host: Move IRQ allocation to
   controller registration phase"), the MHI context gets freed during
   mhi_unregister_controller(). But when the MHI IRQs are shared, the IRQ
   handler may get invoked during __free_irq() if CONFIG_DEBUG_SHIRQ is set.
   In that case, there will be a null pointer dereference because of trying to
   use the freed context struct.

   So for fixing the issue, let's check for the existence of the context struct
   at the start of the handler before handling the IRQ.

----------------------------------------------------------------
Qiang Yu (1):
      bus: mhi: host: Fix up null pointer access in mhi_irq_handler

 drivers/bus/mhi/host/main.c | 19 ++++++++++++++++---
 1 file changed, 16 insertions(+), 3 deletions(-)

-- 
மணிவண்ணன் சதாசிவம்

             reply	other threads:[~2022-08-29 17:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 17:17 Manivannan Sadhasivam [this message]
2022-08-30 14:14 ` [GIT PULL] MHI fixes for v6.0 Greg KH

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=20220829171746.GA84334@thinkpad \
    --to=manivannan.sadhasivam@linaro.org \
    --cc=ath11k@lists.infradead.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kvalo@kernel.org \
    --cc=mhi@lists.linux.dev \
    --cc=quic_hemantk@quicinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).