From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jens Axboe Subject: Re: possible use-after-free in 2.5.44 scsi changes Date: Thu, 31 Oct 2002 16:04:08 +0100 Sender: linux-scsi-owner@vger.kernel.org Message-ID: <20021031150408.GF6549@suse.de> References: <20021030213619.A183086E82@primary.mx.nitric.com> <200210302219.g9UMJ5w05948@eng2.beaverton.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <200210302219.g9UMJ5w05948@eng2.beaverton.ibm.com> List-Id: linux-scsi@vger.kernel.org To: Badari Pulavarty Cc: merlin hughes , linux-scsi@vger.kernel.org On Wed, Oct 30 2002, Badari Pulavarty wrote: > > >- Badari > > > > Hi; if it's of any use, the patch doesn't seem to solve the scsi > > problem for me (2.5.44-bk3-badari). I get the usual 'Incorrect number > > of segments...' and random kernel death during the boot process. > > > > Merlin > > Hi Merlin, > > I am looking at the output of your problem .. > > > Oct 28 12:36:09 badb kernel: Incorrect number of segments after building list > Oct 28 12:36:09 badb kernel: counted 2, received 1 > Oct 28 12:36:09 badb kernel: req nr_sec 8, cur_nr_sec 8 > Oct 28 12:36:09 badb kernel: end_request: I/O error, dev 08:40, sector 6784528 > Oct 28 12:36:09 badb kernel: raid5: Disk failure on scsi/host0/bus0/target4/lun0/part7, disabling device. Operation continuing on 4 devices > > Huh !! Your IO size is only 4K. You are using 2 sg entries ? Even weirder, nr_sec == cur_nr_sec so there can only be one segment or something is corrupted... > Oct 28 12:36:09 badb kernel: blk: request botched which this one also seems to indicate. Merlin, do you have any idea whether older 2.5 kernels worked for you? -- Jens Axboe