From: "Dr. Ernst Molitor" <molitor@uni-bonn.de>
To: James.Bottomley@SteelEye.com
Cc: linux-scsi@vger.kernel.org, "Dr. Ernst Molitor" <molitor@uni-bonn.de>
Subject: Linux-2.6.0-test4: Kernel Panic in scsi_host_dev_release
Date: Mon, 25 Aug 2003 22:54:09 +0200 [thread overview]
Message-ID: <1061844849.486.12.camel@felicia> (raw)
Dear James E.J. Bottomley,
while Linux-2.6.0-test3 runs like a charm on my (testbed) box, I ran
into a kernel panic with Linux-2.6.0-test4 (and 2.6.0-test4-bk4).
The call trace is:
scsi_host_dev_release
device_releases
kobject_cleanup
aha1542_detect
init_this_scsi_driver
do_initcalls
init_workqueues
init
init
kernel_thread_helper
The last line of the panic says:
<0>Kernel Panic: Attempted to kill init!
Assuming the problem lies with the scsi subsystem, I thought you might
perhaps be able to pinpoint the problem.
For what my small knowledge of kernel internals is worth, I looked into
the scsi_host_dev_release function new to drivers/scsi/hosts in
2.6.0-test4. This function receives a struct dev * and extracts an
Scsi_Host pointer from it via the dev_to_shost macro, which, in fact, is
syntactical sugar to the container_of macro.
The predecessor of the scsi_host_dev_release function in 2.6.0-test3 was
scsi_free_shost (which had a parameter of type Scsi_Host *).
The last line of both functions is identical: kfree is called with the
pointer shost. From a very superficial analysis, I would feel that
freeing *dev rather than *shost would be logical, but I might very well
be way off the real source of the panic I have seen.
If you'd like me to, I could provide the full kernel panic message
(since the system is far from booted when the panic occurrs, I don't
have any trace of this on my disks...).
Kind regards,
Yours
Ernst Molitor
next reply other threads:[~2003-08-25 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 20:54 Dr. Ernst Molitor [this message]
2003-08-25 23:42 ` Linux-2.6.0-test4: Kernel Panic in scsi_host_dev_release Mike Anderson
2003-08-26 7:20 ` Dr. Ernst Molitor
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=1061844849.486.12.camel@felicia \
--to=molitor@uni-bonn.de \
--cc=James.Bottomley@SteelEye.com \
--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 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.