All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yum Rayan <yum.rayan@gmail.com>
To: Klaus.Steinberger@physik.uni-muenchen.de, linux-scsi@vger.kernel.org
Cc: rddunlap@osdl.org
Subject: RE: Kernel OOPS with aacraid driver
Date: Fri, 22 Apr 2005 00:08:53 -0700	[thread overview]
Message-ID: <df35dfeb050422000856c882d6@mail.gmail.com> (raw)

> > BTW, this says that this is the second oops:  "[#2]".
> > What was the first one?
> Apr 21 10:53:27 www adaptec-smbe: aiomgrd startup succeeded
> Apr 21 10:53:27 www kernel: Unable to handle kernel NULL 
> pointer dereference 
> at virtual address 00000034

Seems to me like someone is issuing IOCTL's against devices that do
not exist. Does this patch against linux-2.6.12-rc3 make sense and
applicable to you?

Seems like aac_cfg_open() will return success even if it fails? This
patch fixes it to actually return error.

Regards,
Rayan

diff -Nupr -X dontdiff linux-2.6.12-rc3.a/drivers/scsi/aacraid/linit.c
linux-2.6.12-rc3.b/drivers/scsi/aacraid/linit.c
--- linux-2.6.12-rc3.a/drivers/scsi/aacraid/linit.c	2005-04-21
23:56:31.000000000 -0700
+++ linux-2.6.12-rc3.b/drivers/scsi/aacraid/linit.c	2005-04-21
23:57:26.000000000 -0700
@@ -450,7 +450,7 @@ static int aac_cfg_open(struct inode *in
 		}
 	}
 
-	return 0;
+	return err;
 }
 
 /**

             reply	other threads:[~2005-04-22  7:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-22  7:08 Yum Rayan [this message]
2005-04-22 11:57 ` Kernel OOPS with aacraid driver Klaus Steinberger
2005-04-24  9:41   ` Klaus Steinberger
2005-04-22 15:42 ` Mark Haverkamp
  -- strict thread matches above, loose matches on Subject: below --
2005-04-22  5:49 Klaus Steinberger
2005-04-22  6:27 ` Randy.Dunlap
2005-04-22  6:49   ` Klaus Steinberger

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=df35dfeb050422000856c882d6@mail.gmail.com \
    --to=yum.rayan@gmail.com \
    --cc=Klaus.Steinberger@physik.uni-muenchen.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rddunlap@osdl.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.