From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Greg Kroah-Hartman <greg@kroah.com>
Cc: schwidefsky@de.ibm.com,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] s390 (8/10): zfcp fixes
Date: Wed, 31 Mar 2004 19:57:18 +0200 [thread overview]
Message-ID: <200403311957.18451.heiko.carstens@de.ibm.com> (raw)
Hi Greg,
>> I'll ask because the zfcp patches are still pending and I want to get this
>> issue resolved before the next try to get them integrated.
>I think you need to talk to the scsi people, as kfree() should _never_
>need to be set as the release function. There's something just wrong
>with the design if that is necessary.
Actually this issue is not SCSI related, but a generic problem that one
can run into when fiddling around with modules / module unloading.
This was already discussed elsewhere. Please have a look here:
http://lwn.net/Articles/67421/
(paragraph "Module unloading in a reference counted world")
and here for the whole thread:
http://www.ussg.iu.edu/hypermail/linux/kernel/0401.2/1832.html
(just saw that you participated there :)
I would be more than happy to have a nice release function for the zfcp
generated objects, but I don't think this is currently possible without
having the potential problem to run into an Oops after module unloading.
Heiko
next reply other threads:[~2004-03-31 17:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 17:57 Heiko Carstens [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-29 10:03 [PATCH] s390 (8/10): zfcp fixes Martin Schwidefsky
2004-03-30 1:37 ` Greg KH
2004-03-17 12:06 Martin Schwidefsky
2004-03-16 13:51 Martin Schwidefsky
2004-03-16 21:52 ` James Bottomley
2004-03-17 10:35 ` Heiko Carstens
2004-03-12 20:29 Martin Schwidefsky
2004-03-13 1:41 ` Greg KH
2004-03-15 9:18 ` Martin Schwidefsky
2004-03-16 17:08 ` Greg KH
2004-03-12 19:38 Martin Schwidefsky
2004-03-12 20:19 ` Christoph Hellwig
2004-03-13 1:40 ` Greg KH
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=200403311957.18451.heiko.carstens@de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).