From: "jackylam" <jackylam@astri.org>
To: linux-kernel@vger.kernel.org
Subject: Buffer overflow in SCSI code?
Date: Sun, 23 Nov 2003 10:13:42 +0800 [thread overview]
Message-ID: <3fc017d6.504e.1139768128@astri.org> (raw)
Dear all,
I am not very experience in SCSI. Currently, I try to
play with a ITE8212F PCI IDE RAID card. After compiling and
insert the driver module, there will be a kernel fault when
accessing file greater than 4K. After tracing the problem up
to kernel SCSI level, I find something very strange in the
SCSI buffer allocation.
Here is the log:
.
.
.
SMalloc: 512 c03af000 [From:00000007]
SMalloc: 512 c03af000 [From:00000007]
Doing sd request, dev = 0x801, block = 62128
sda : real dev = /dev/0, block = 62191
sda : reading 32/32 512 byte blocks.
Adding timer for command d8ef7600 at 3000 (c0217700)
scsi_dispatch_cmnd (host = 1, channel = 0, target = 0,
command = d8ef7658, buffer = c03af000,
bufflen = 16384, done = c02295c0)
.
.
.
It is showing that the buffer 0xc03af000 is allocated
for 512 bytes only. However, it is used to hold 16K data in
the following code. And this pointer will finally pass to
the ITE driver.
Can anyone explain to me that is it correct? Thanks.
Best regards,
Jacky
reply other threads:[~2003-11-23 2:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3fc017d6.504e.1139768128@astri.org \
--to=jackylam@astri.org \
--cc=faichai0@yahoo.com \
--cc=linux-kernel@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