From: Mike Anderson <andmike@us.ibm.com>
To: Thomas Molina <tmolina@cox.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ide-scsi segfaults under 2.5.44
Date: Sun, 20 Oct 2002 11:18:25 -0700 [thread overview]
Message-ID: <20021020181825.GA3915@beaverton.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0210192229310.891-100000@dad.molina>
Thomas,
It looks like sg.c was missed in the update from put_device to
device_unregister.
I have only compile tested the patch below, but it should fix the
problem. I will have a chance to run later on today.
Thomas Molina [tmolina@cox.net] wrote:
> Oct 19 22:10:30 dad kernel: [<d905f780>]
> scsi_driverfs_bus_type_Rfc6baff9+0x0/0x80 [scsi_mod]
> Oct 19 22:10:30 dad kernel: [<c01d0b78>] put_driver+0x28/0x50
> Oct 19 22:10:30 dad kernel: [<d9097028>] sg_template+0x48/0xa0 [sg]
> Oct 19 22:10:30 dad kernel: [<d90928ac>] exit_sg+0x4c/0x50 [sg]
> Oct 19 22:10:30 dad kernel: [<d9097028>] sg_template+0x48/0xa0 [sg]
> Oct 19 22:10:30 dad kernel: [<c0119e1e>] free_module+0x1e/0xb0
> Oct 19 22:10:30 dad kernel: [<c01192f7>] sys_delete_module+0xe7/0x1c0
> Oct 19 22:10:30 dad kernel: [<c0108adf>] syscall_call+0x7/0xb
> Oct 19 22:10:30 dad kernel:
-andmike
--
Michael Anderson
andmike@us.ibm.com
sg.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
------
===== drivers/scsi/sg.c 1.30 vs edited =====
--- 1.30/drivers/scsi/sg.c Fri Oct 18 11:27:30 2002
+++ edited/drivers/scsi/sg.c Sun Oct 20 10:59:33 2002
@@ -1607,7 +1607,7 @@
sdp->de = NULL;
device_remove_file(&sdp->sg_driverfs_dev, &dev_attr_type);
device_remove_file(&sdp->sg_driverfs_dev, &dev_attr_kdev);
- put_device(&sdp->sg_driverfs_dev);
+ device_unregister(&sdp->sg_driverfs_dev);
if (NULL == sdp->headfp)
vfree((char *) sdp);
}
next prev parent reply other threads:[~2002-10-20 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-20 3:39 Thomas Molina
2002-10-20 18:18 ` Mike Anderson [this message]
2002-10-20 20:53 ` Thomas Molina
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=20021020181825.GA3915@beaverton.ibm.com \
--to=andmike@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tmolina@cox.net \
/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
Powered by JetHome