mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: chengkaitao <pilgrimtao@gmail.com>
To: kashyap.desai@broadcom.com, sumit.saxena@broadcom.com,
	shivasharan.srikanteshwara@broadcom.com,
	chandrakanth.patil@broadcom.com,
	James.Bottomley@HansenPartnership.com,
	martin.petersen@oracle.com
Cc: megaraidlinux.pdl@broadcom.com, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Chengkaitao <chengkaitao@kylinos.cn>
Subject: [RFC RESEND 0/2] megaraid: fix illegal pointer dereference in complete_cmd_fusion
Date: Sun,  1 Feb 2026 11:31:08 +0800	[thread overview]
Message-ID: <20260201033110.34297-1-pilgrimtao@gmail.com> (raw)

From: Chengkaitao <chengkaitao@kylinos.cn>

We have encountered several instances of null pointer dereferences
in the complete_cmd_fusion function. The root cause was consistently
the reply_desc->SMID being erroneously set to 0xffff, resulting in
an invalid cmd_fusion pointer retrieval.

After code review, I suspect synchronization issues in complete_cmd-
_fusion. However, due to the low reproducibility rate of this problem,
I could not perform effective validation. I propose the patch for
kernel community discussion to explore better solutions.

Chengkaitao (2):
  megaraid: Fix the issue of erroneous reset of Words in reply_desc
  megaraid: replacing fusion->busy_mq_poll[*] with irq_context->in_used
    in megasas_blk_mq_poll

 drivers/scsi/megaraid/megaraid_sas_fusion.c | 18 ++++++++++--------
 drivers/scsi/megaraid/megaraid_sas_fusion.h |  2 --
 2 files changed, 10 insertions(+), 10 deletions(-)

-- 
2.50.1 (Apple Git-155)


             reply	other threads:[~2026-02-01  3:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-01  3:31 chengkaitao [this message]
2026-02-01  3:31 ` [RFC RESEND 1/2] megaraid: Fix the issue of erroneous reset of Words in reply_desc chengkaitao
2026-02-01  3:31 ` [RFC RESEND 2/2] megaraid: replacing fusion->busy_mq_poll[*] with irq_context->in_used in megasas_blk_mq_poll chengkaitao

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=20260201033110.34297-1-pilgrimtao@gmail.com \
    --to=pilgrimtao@gmail.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=chandrakanth.patil@broadcom.com \
    --cc=chengkaitao@kylinos.cn \
    --cc=kashyap.desai@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=megaraidlinux.pdl@broadcom.com \
    --cc=shivasharan.srikanteshwara@broadcom.com \
    --cc=sumit.saxena@broadcom.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

all inboxes | Powered by JetHome®