public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Linux Kernel Developer <linux_developer@hotmail.com>
Cc: J Sloan <jjs@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: CPQARRAY driver horribly broken in 2.4.14
Date: Sat, 10 Nov 2001 14:37:58 +0100	[thread overview]
Message-ID: <20011110143758.D17902@suse.de> (raw)
In-Reply-To: <F5uLCTaogxLDp7mvjkO00000742@hotmail.com> <3BEB5149.B0B7990F@pobox.com> <OE36joYAPNXRPmcarcR0001ece1@hotmail.com>
In-Reply-To: <OE36joYAPNXRPmcarcR0001ece1@hotmail.com>

[-- Attachment #1: Type: text/plain, Size: 852 bytes --]

On Fri, Nov 09 2001, Linux Kernel Developer wrote:
> Hi,
> 
>     Thanks a lot for the help.  Any particular reason to use the new driver
> now or should I just wait until 2.4.15 is release?
> 
>     Guess I didn't need to do all that debugging.  Bug may have already been
> caught.  8-)
> 
>     However I did notice something.  The patch you've included below covers
> the cciss.c file?  My system is using the cpqarray driver.  And I fixed the
> problem by replacing the cpqarray.[ch], ida_cmd.h, and ida_ioctl.h files.  I
> don't think the patch below would have done anything for me as I'm pretty
> sure the cciss.c file isn't used by the cpqarray driver and since I didn't
> change out the cciss.c file in my now working kernel source tree (linux
> 2.4.14-lkd1 8-D).

You needed the cciss equivalent of the one posted, attached.

-- 
Jens Axboe


[-- Attachment #2: cciss-dequeue-1 --]
[-- Type: text/plain, Size: 625 bytes --]

--- linux/drivers/block/cciss.c~	Thu Nov  8 11:36:24 2001
+++ linux/drivers/block/cciss.c	Thu Nov  8 11:37:03 2001
@@ -1307,6 +1307,8 @@
 	if (( c = cmd_alloc(h, 1)) == NULL)
 		goto startio;
 
+	blkdev_dequeue_request(creq);
+
 	spin_unlock_irq(&io_request_lock);
 
 	c->cmd_type = CMD_RWREQ;      
@@ -1386,12 +1388,6 @@
 
 	spin_lock_irq(&io_request_lock);
 
-	blkdev_dequeue_request(creq);
-
-        /*
-         * ehh, we can't really end the request here since it's not
-         * even started yet. for now it shouldn't hurt though
-         */
 	addQ(&(h->reqQ),c);
 	h->Qdepth++;
 	if(h->Qdepth > h->maxQsinceinit)

      reply	other threads:[~2001-11-10 13:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-09  3:04 CPQARRAY driver horribly broken in 2.4.14 Linux Kernel Developer
2001-11-09  3:45 ` J Sloan
2001-11-09 21:51   ` Linux Kernel Developer
2001-11-10 13:37     ` Jens Axboe [this message]

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=20011110143758.D17902@suse.de \
    --to=axboe@suse.de \
    --cc=jjs@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_developer@hotmail.com \
    /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