From: Willem Riede <wriede@home.com>
To: Dawson Engler <engler@csl.Stanford.EDU>
Cc: linux-kernel@vger.kernel.org, mc@cs.Stanford.EDU
Subject: Re: [CHECKER] null bugs in 2.4.4 and 2.4.4-ac8
Date: Thu, 24 May 2001 18:06:30 -0400 [thread overview]
Message-ID: <3B0D85E6.7E509F3E@home.com> (raw)
In-Reply-To: <200105242109.OAA29748@csl.Stanford.EDU>
Dawson Engler wrote:
>
> Hi All,
>
> Enclosed are 103 potential errors where code gets a pointer from a
> possibly-failing routine (kmalloc, etc) and dereferences it without
>
> [BUG] osst_do_scsi will never return NULL if argument SRpnt isn't NULL. But they copy SRpnt back by *aSRpnt, implies it could be NULL
No. It implies SRpnt could have changed. The functions flagged
(osst_read_back_buffer_and_rewrite and osst_reposition_and_retry)
cannot be reached with SRpnt == NULL. So these are false alarms.
> /u2/engler/mc/oses/linux/2.4.4/drivers/scsi/osst.c:1163:osst_read_back_buffer_and_rewrite: ERROR:NULL:1111:1163: Using unknown ptr "SRpnt" illegally! set by 'osst_do_scsi':1163 [nbytes = 216]
> #if DEBUG
> if (debugging)
> printk(OSST_DEB_MSG "osst%d: About to attempt to write to frame %d\n", dev, new_block+i);
> #endif
> SRpnt = osst_do_scsi(SRpnt, STp, cmd, OS_FRAME_SIZE, SCSI_DATA_WRITE,
> Start --->
> STp->timeout, MAX_WRITE_RETRIES, TRUE);
>
> ... DELETED 46 lines ...
>
> }
> }
> if (flag) {
> if ((SRpnt->sr_sense_buffer[ 2] & 0x0f) == 13 &&
> SRpnt->sr_sense_buffer[12] == 0 &&
> Error --->
> SRpnt->sr_sense_buffer[13] == 2) {
> printk(KERN_ERR "osst%d: Volume overflow in write error recovery\n", dev);
> vfree((void *)buffer);
> return (-EIO); /* hit end of tape = fail */
>
Regards. Willem Riede.
next prev parent reply other threads:[~2001-05-24 22:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 21:09 [CHECKER] null bugs in 2.4.4 and 2.4.4-ac8 Dawson Engler
2001-05-24 22:06 ` Willem Riede [this message]
2001-05-24 22:38 ` Junfeng Yang
2001-05-25 0:00 ` Willem Riede
2001-05-24 22:26 ` Anton Altaparmakov
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=3B0D85E6.7E509F3E@home.com \
--to=wriede@home.com \
--cc=engler@csl.Stanford.EDU \
--cc=linux-kernel@vger.kernel.org \
--cc=mc@cs.Stanford.EDU \
/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.