linux-kernel - Re: 2.6.22 oops kernel BUG at block/elevator.c:366!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070829181648.GD7932@kernel.dk>
Date:	Wed, 29 Aug 2007 20:16:48 +0200
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Arkadiusz Miskiewicz <arekm@...en.pl>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.22 oops kernel BUG at block/elevator.c:366!

On Wed, Aug 29 2007, Arkadiusz Miskiewicz wrote:
> On Wednesday 29 of August 2007, Jens Axboe wrote:
> > On Wed, Aug 29 2007, Arkadiusz Miskiewicz wrote:
> > > On Wednesday 29 of August 2007, Jens Axboe wrote:
> > > > On Wed, Aug 29 2007, Arkadiusz Miskiewicz wrote:
> > > > > I guess I should sent these here since it looks like not scsi bug
> > > > > anyway.
> > > >
> > > > It's stex, right? It seems to have some issues with multiple
> > > > completions of commands, which craps out the block layer of course.
> > >
> > > Yes, stex. I'm staying with 2.6.19 in that case since it works fine in
> > > that version.
> > >
> > > So scsi bug ... 8-)
> >
> > And you based that conclusion on what exactly?
> 
> Isn't drivers/scsi/* handled by linux-scsi@? (that's what I mean)

Yep indeed, I thought you meant that it was a scsi bug (and not an stex
one). You could try and copy the 2.6.19 stex driver into 2.6.20 and see
if that works, though.

-- 
Jens Axboe

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/