From: Jens Axboe <axboe@suse.de>
To: merlin <merlin@merlin.org>
Cc: Badari Pulavarty <badari@us.ibm.com>, linux-scsi@vger.kernel.org
Subject: Re: possible use-after-free in 2.5.44 scsi changes
Date: Thu, 31 Oct 2002 15:46:53 +0100 [thread overview]
Message-ID: <20021031144653.GE6549@suse.de> (raw)
In-Reply-To: <20021031144103.103D286E73@primary.mx.nitric.com>
On Thu, Oct 31 2002, merlin wrote:
> r/axboe@suse.de/2002.10.31/14:18:24
> >On Wed, Oct 30 2002, merlin wrote:
> >> Hi Badari,
> >>
> >> I grabbed 2.5.45 and added the printks you describe.. The kernel
> >> dies before the syslog is written and I don't have a serial device
> >> to try capturing the output there, but this is what I scribbled
> >> down:
> >>
> >> ...lots of stuff ...
> >> home: clean
> >> made a new seg: 1 (c18adc70, 4096, 0)
> >> Loop: brvprv: c18adc70 bvec:c18ad838 offset:0 length:4096
> >> made a new seg: 2 (c18ad838, 4096, 0)
> >> returning segs: 2
> >> Incorrect number of segments after building list
> >> counted 2, received 1
> >> ...some stuff...
> >>
> >> Things went on for a few more messages before the kernel died
> >> a death.
> >>
> >> It's an SMP box so the seg stuff that precedes the error may
> >> be unrelated; I don't have a good enough grasp to be sure. I
> >> guess an interesting value to know might be max_segment_size.
> >>
> >> Half tempted to try a non-SMP build, just to see. Each time I
> >> do this, I get a bit more (recoverable) fs damage, but still..
> >
> >SMP should not make a difference. Does this patch make a difference?
>
> Same error I'm afraid; ``Incorrect number of segments after building list
> counted 2, received 1'' follows shortly by kernel panic..
in drivers/scsi/aic7xxx/aic7xxx_linux_host.h:83, change
ENABLE_CLUSTERING to DISABLE_CLUSTERING and repeat the test, please.
--
Jens Axboe
next prev parent reply other threads:[~2002-10-31 14:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 1:39 possible use-after-free in 2.5.44 scsi changes Andrew Morton
2002-10-25 4:06 ` Doug Ledford
2002-10-25 4:40 ` Andrew Morton
2002-10-25 14:21 ` James Bottomley
2002-10-25 4:07 ` Patrick Mansfield
2002-10-25 14:16 ` James Bottomley
2002-10-25 18:34 ` James Bottomley
2002-10-25 18:49 ` Mike Anderson
2002-10-25 19:08 ` Patrick Mansfield
2002-10-25 19:41 ` Mike Anderson
2002-10-25 19:47 ` Jens Axboe
2002-10-25 22:14 ` James Bottomley
2002-10-25 22:18 ` Andrew Morton
2002-10-25 22:23 ` Badari Pulavarty
2002-10-26 0:13 ` James Bottomley
2002-10-26 0:18 ` Mike Anderson
2002-10-26 9:29 ` Jens Axboe
2002-10-27 0:50 ` James Bottomley
2002-10-27 21:20 ` Jens Axboe
2002-10-27 21:37 ` James Bottomley
2002-10-27 21:54 ` Jens Axboe
2002-10-30 17:39 ` Badari Pulavarty
2002-10-30 18:16 ` Jens Axboe
2002-10-30 19:31 ` Badari Pulavarty
2002-10-30 21:36 ` merlin hughes
2002-10-30 22:19 ` Badari Pulavarty
2002-10-31 2:17 ` merlin
2002-10-31 13:18 ` Jens Axboe
2002-10-31 14:41 ` merlin
2002-10-31 14:46 ` Jens Axboe [this message]
2002-10-31 15:04 ` Jens Axboe
2002-10-31 15:12 ` Jens Axboe
2002-10-31 17:41 ` merlin
2002-10-30 20:35 ` David S. Miller
2002-10-30 22:03 ` Badari Pulavarty
-- strict thread matches above, loose matches on Subject: below --
2002-10-31 17:57 Badari Pulavarty
2002-10-31 18:46 ` Jens Axboe
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=20021031144653.GE6549@suse.de \
--to=axboe@suse.de \
--cc=badari@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=merlin@merlin.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 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.