From: Andrew Morton <akpm@osdl.org>
To: Diffie <diffie@blazebox.homeip.net>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Badness in device_release at drivers/base/core.c:84
Date: Sat, 2 Aug 2003 19:07:37 -0700 [thread overview]
Message-ID: <20030802190737.3c41d4d8.akpm@osdl.org> (raw)
In-Reply-To: <20030803015510.GB4696@blazebox.homeip.net>
Diffie <diffie@blazebox.homeip.net> wrote:
>
> After applaying the above patch and testing it still oopses the kernel.
>
> I noticed same patch in today's mm3 which i compiled and use right now.
>
> When using cat /proc/scsi/aic7xxx/0 i get segmentation fault and oops
> which i'll attach to this email.
>
> ...
>
> EIP is at aic7xxx_proc_info+0xc28/0xc80
This is crashing in a different place. Probably the same bug, showing up
later on.
I don't know if anyone is maintaining aic7xxx_old in 2.7. It looks like it
was subject to some random untested change a couple of months back.
next prev parent reply other threads:[~2003-08-03 2:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030801182207.GA3759@blazebox.homeip.net>
2003-08-01 21:44 ` Badness in device_release at drivers/base/core.c:84 Andrew Morton
2003-08-01 23:27 ` Mike Anderson
[not found] ` <20030803015510.GB4696@blazebox.homeip.net>
2003-08-03 2:07 ` Andrew Morton [this message]
2003-08-03 21:47 ` Diffie
2003-08-03 21:52 ` Andrew Morton
2003-08-03 22:23 ` Diffie
2003-08-03 22:31 ` Diffie
2003-08-04 16:30 ` Patrick Mansfield
2003-08-04 17:48 ` Paul Blazejowski
2003-08-04 18:26 ` Paul Blazejowski
2003-08-04 18:57 ` Patrick Mansfield
2003-08-04 19:36 ` Justin T. Gibbs
2003-08-05 2:21 ` Paul Blazejowski
2003-08-05 10:20 ` wb
2003-08-05 16:10 ` Ishikawa
2003-08-06 16:58 ` Paul Blazejowski
2003-08-06 17:20 ` Chiaki
2003-08-13 2:03 ` Chiaki
2003-08-06 16:55 ` Paul Blazejowski
2003-08-05 7:18 ` Paul Blazejowski
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=20030802190737.3c41d4d8.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=diffie@blazebox.homeip.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox