From: christophe varoqui <christophe.varoqui@free.fr>
To: James Bottomley <James.Bottomley@steeleye.com>,
linux-scsi@vger.kernel.org
Subject: Re: [bug]
Date: Tue, 02 Mar 2004 00:04:18 +0100 [thread overview]
Message-ID: <4043C172.1060800@free.fr> (raw)
In-Reply-To: <1078181191.1804.82.camel@mulgrave>
>
> Unfortunately, without the top of the trace showing what happened and in
> which function, it's fairly difficult to debug what went on.
>
> Could you attach a serial console and reproduce, so you can get the
> whole trace?
>
mm, digging this, I traced the bug to an sg_inq in my userspace code :
do_inq(fd, 0, 1, 0x83, buff, 64, 1);
seting the size of the buff to a higher value (#define MX_ALLOC_LEN 255)
mutes the oops. Dunno what happened, it worked with size = 64 until
recently.
For completeness, the bug triggered at modprobe qla2200 because my code
got exec'ed by scsi hotplug events.
regards,
cvaroqui
next prev parent reply other threads:[~2004-03-01 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 22:00 [bug] christophe varoqui
2004-03-01 22:46 ` [bug] James Bottomley
2004-03-01 23:04 ` christophe varoqui [this message]
2004-03-05 5:54 ` [bug] Andrew Vasquez
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=4043C172.1060800@free.fr \
--to=christophe.varoqui@free.fr \
--cc=James.Bottomley@steeleye.com \
--cc=linux-scsi@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