public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Hamza Mahfooz <hamzamahfooz@linux.microsoft.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Guixin Liu <kanie@linux.alibaba.com>,
	Nicholas Bellinger <nab@linux-iscsi.org>,
	Sheng Yang <sheng@yasker.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"target-devel@vger.kernel.org" <target-devel@vger.kernel.org>,
	Allen Pais <apais@linux.microsoft.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] scsi: target: tcm_loop: fix segfault in tcm_loop_tpg_address_show()
Date: Thu, 6 Nov 2025 06:41:00 +0000	[thread overview]
Message-ID: <2c70e9bf-e6fb-4443-bfc9-fab448fb2f65@nvidia.com> (raw)
In-Reply-To: <1762370746-6304-1-git-send-email-hamzamahfooz@linux.microsoft.com>

On 11/5/25 11:25, Hamza Mahfooz wrote:
> If the allocation of tl_hba->sh fails in tcm_loop_driver_probe() and we
> attempt to dereference it in tcm_loop_tpg_address_show() we will get a
> segfault, see below for an example. So, check tl_hba->sh before
> dereferencing it.
>
>    Unable to allocate struct scsi_host
>    BUG: kernel NULL pointer dereference, address: 0000000000000194
>    #PF: supervisor read access in kernel mode
>    #PF: error_code(0x0000) - not-present page
>    PGD 0 P4D 0
>    Oops: 0000 [#1] PREEMPT SMP NOPTI
>    CPU: 1 PID: 8356 Comm: tokio-runtime-w Not tainted 6.6.104.2-4.azl3 #1
>    Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 09/28/2024
>    RIP: 0010:tcm_loop_tpg_address_show+0x2e/0x50 [tcm_loop]
> ...
>    Call Trace:
>     <TASK>
>     configfs_read_iter+0x12d/0x1d0 [configfs]
>     vfs_read+0x1b5/0x300
>     ksys_read+0x6f/0xf0
> ...
>
> Cc:stable@vger.kernel.org
> Fixes: 2628b352c3d4 ("tcm_loop: Show address of tpg in configfs")
> Signed-off-by: Hamza Mahfooz<hamzamahfooz@linux.microsoft.com>
> ---


indeed :-

  313 static int tcm_loop_driver_probe(struct device *dev)
  314 {
  315         struct tcm_loop_hba *tl_hba;
  316         struct Scsi_Host *sh;
  317         int error, host_prot;
  318
  319         tl_hba = to_tcm_loop_hba(dev);
  320
  321         sh = scsi_host_alloc(&tcm_loop_driver_template,
  322                         sizeof(struct tcm_loop_hba));
  323         if (!sh) {
  324                 pr_err("Unable to allocate struct scsi_host\n");
  325                 return -ENODEV;
  326         }
  327         tl_hba->sh = sh;


Looks good.

Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>

-ck



  reply	other threads:[~2025-11-06  6:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 19:25 [PATCH] scsi: target: tcm_loop: fix segfault in tcm_loop_tpg_address_show() Hamza Mahfooz
2025-11-06  6:41 ` Chaitanya Kulkarni [this message]
2025-11-06 15:56 ` Allen Pais
2025-11-13  2:47 ` Martin K. Petersen

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=2c70e9bf-e6fb-4443-bfc9-fab448fb2f65@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=apais@linux.microsoft.com \
    --cc=hamzamahfooz@linux.microsoft.com \
    --cc=kanie@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=nab@linux-iscsi.org \
    --cc=sheng@yasker.org \
    --cc=stable@vger.kernel.org \
    --cc=target-devel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox