All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Oliver Jehle <oliver.jehle@monex.li>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problems using /proc/scsi/gdth/ with 2.4.20aa1
Date: Wed, 11 Dec 2002 18:03:17 -0500	[thread overview]
Message-ID: <20021211230317.GD6513@redhat.com> (raw)
In-Reply-To: <1039502939.1054.12.camel@vorab.monex.li>

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

On Tue, Dec 10, 2002 at 07:49:00AM +0100, Oliver Jehle wrote:
> Running linux 2.4.20-aa1 and the gdth driver works ,but accessing
> /proc/scsi/gdth/0 for example with cat or the supplied icpcon utility
> don't work...
> 
> these messages are in system log when accessing /proc/scsi/gdth/0 with
> cat for example (works with 2.4.18)
> ...
> 
> Dec 10 06:37:47 arena1 kernel: Unable to handle kernel NULL pointer
> dereference at virtual address 00000000
> Dec 10 06:37:47 arena1 kernel:  printing eip:
> Dec 10 06:37:47 arena1 kernel: c024c879
> Dec 10 06:37:47 arena1 kernel: *pde = 00000000
> Dec 10 06:37:47 arena1 kernel: Oops: 0002 2.4.20aa1 #2 SMP Mon Dec 9
> 16:55:18 CET 2002
> Dec 10 06:37:47 arena1 kernel: CPU:    0
> Dec 10 06:37:47 arena1 kernel: EIP:   
> 0010:[scsi_release_commandblocks+17/92]    Not tainted

/me chuckles

That looks *amazingly* familiar...a patch I wrote introduced that bug,
sorry.  It's fix is attached (assuming that Andrea picked up the same
version of the 2.4.x iorl contention patch that we are using now, which 
is what introduced this problem for us here).

-- 
  Doug Ledford <dledford@redhat.com>     919-754-3700 x44233
         Red Hat, Inc. 
         1801 Varsity Dr.
         Raleigh, NC 27606
  

[-- Attachment #2: linux-2.4.9-gdthoops.patch --]
[-- Type: text/plain, Size: 745 bytes --]

--- linux/drivers/scsi/scsi.c-stock	Fri Oct 25 15:41:03 2002
+++ linux/drivers/scsi/scsi.c	Fri Oct 25 15:47:04 2002
@@ -2672,10 +2672,10 @@
         SDpnt->type = -1;
         SDpnt->queue_depth = 1;
         
-	scsi_build_commandblocks(SDpnt);
-
 	scsi_initialize_queue(SDpnt, SHpnt);
 
+	scsi_build_commandblocks(SDpnt);
+
 	SDpnt->online = TRUE;
 
         /*
@@ -2705,13 +2705,12 @@
                 panic("Attempt to delete wrong device\n");
         }
 
-        blk_cleanup_queue(&SDpnt->request_queue);
-
         /*
          * We only have a single SCpnt attached to this device.  Free
          * it now.
          */
 	scsi_release_commandblocks(SDpnt);
+        blk_cleanup_queue(&SDpnt->request_queue);
         kfree(SDpnt);
 }
 

      reply	other threads:[~2002-12-11 22:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10  6:49 Problems using /proc/scsi/gdth/ with 2.4.20aa1 Oliver Jehle
2002-12-11 23:03 ` Doug Ledford [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=20021211230317.GD6513@redhat.com \
    --to=dledford@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver.jehle@monex.li \
    /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.