From: Greg KH <greg@kroah.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390 (8/10): zfcp fixes.
Date: Tue, 16 Mar 2004 09:08:12 -0800 [thread overview]
Message-ID: <20040316170812.GA14971@kroah.com> (raw)
In-Reply-To: <OF625BA2CA.1376AB85-ONC1256E58.002FCAD7-C1256E58.00331651@de.ibm.com>
On Mon, Mar 15, 2004 at 10:18:00AM +0100, Martin Schwidefsky wrote:
>
> So we need an external release function, one that isn't part of the zfcp
> module. This external release function is either a generic function for
> all these objects or a dedicated release function for each of the
> additional
> device objects. A dedicated release function would mean to define a release
> function somewhere in the kernel or another module just for the purpose of
> freeing an object defined by the zfcp module. This is even more gross than
> to use a generic release function. And the simplest release function is
> kfree.
This is not ok. If you have to do something like this, I really suggest
that you not allow the "sub modules" be able to unload before the upper
module can. In fact, why would you want to do such a thing?
I still really strongly object to this patch. If it's a scsi problem,
fix it there, but odds are it's your driver's problem as no other scsi
driver needs this.
thanks,
greg k-h
next prev parent reply other threads:[~2004-03-16 17:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 20:29 [PATCH] s390 (8/10): zfcp fixes Martin Schwidefsky
2004-03-13 1:41 ` Greg KH
2004-03-15 9:18 ` Martin Schwidefsky
2004-03-16 17:08 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-31 17:57 Heiko Carstens
2004-03-29 10:03 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 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=20040316170812.GA14971@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--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