From: Stephan von Krawczynski <skraw@ithnet.com>
To: "Peter Wong" <wpeter@us.ibm.com>
Cc: Jens Axboe <axboe@suse.de>,
marcelo@conectiva.com.br, Pete Zaitcev <zaitcev@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Encountered a Null Pointer Problem on the SCSI Layer
Date: Tue, 19 Feb 2002 00:01:39 +0100 [thread overview]
Message-ID: <200202182301.AAA23425@webserver.ithnet.com> (raw)
In-Reply-To: <OFC7A42817.7DD2C3FB-ON85256B64.00725D00@raleigh.ibm.com>
> A while ago, I reported that I encountered a null pointer problem
> on the SCSI layer when I was testing Mingming Cao's diskio patch
> "diskio-stat-rq-2414" on 2.4.14.
>
> Mingming's patch is at http://sourceforge.net/projects/lse/.
>
> The code in sd_find_queue() that protects against accessing a
> non-existent device is not correct. After my patch was sent out,
> Pete Zaitcev of Red Hat identified a similar problem in
> sd_init_command of the same file.
>
> Let's consider sd_find_queue().
>
> If the array pointed by rscsi_disk has been allocated,
> dpnt cannot be null.
>
> If rscsi_disk has NOT been allocated, dpnt =
&rscsi_disks[target]
> may NOT be null, and it depends on the value of target. Thus,
> "if (!dpnt)" is not sufficient anyway.
>
> You can also look at sd_attach(), in which "if (!dpnt->device)"
is
> tested, not "if (!dpnt)".
>
> Please check.
Are you 100% sure, that there is no case where
dpnt==NULL? Because if there is such a possibility, your patch will
blow up.
It would be completely safe to check both
(!dpnt && !dpnt->device)
Regards,
Stephan
>
> The following patch is based on the 2.4.18-pre7 code:
>
----------------------------------------------------------------------
-----
> --- linux/drivers/scsi/sd.c Mon Feb 18 13:36:42 2002
> +++ linux-2.4.17-diskio/drivers/scsi/sd.c Mon Feb 18 13:29:34 2002
> @@ -279,7 +279,7 @@
> target = DEVICE_NR(dev);
>
> dpnt = &rscsi_disks[target];
> - if (!dpnt)
> + if (!dpnt->device)
> return NULL; /* No such device */
> return &dpnt->device->request_queue;
> }
> @@ -302,7 +302,7 @@
>
> dpnt = &rscsi_disks[dev];
> if (devm >= (sd_template.dev_max << 4) ||
> - !dpnt ||
> + !dpnt->device ||
> !dpnt->device->online ||
> block + SCpnt->request.nr_sectors > sd[devm].nr_sects) {
> SCSI_LOG_HLQUEUE(2, printk("Finishing %ld sectors\n",
SCpnt->request.nr_sectors));
>
----------------------------------------------------------------------
-----
>
> Regards,
> Peter
>
> Wai Yee Peter Wong
> IBM Linux Technology Center, Performance Analysis
> email: wpeter@us.ibm.com
>
> -
> To unsubscribe from this list: send the line "unsubscribe
linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2002-02-18 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-18 21:03 [PATCH] Encountered a Null Pointer Problem on the SCSI Layer Peter Wong
2002-02-18 23:01 ` Stephan von Krawczynski [this message]
2002-02-19 0:04 ` Pete Zaitcev
2002-02-19 11:55 ` Stephan von Krawczynski
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=200202182301.AAA23425@webserver.ithnet.com \
--to=skraw@ithnet.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=wpeter@us.ibm.com \
--cc=zaitcev@redhat.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