All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Heiko Carstens <Heiko.Carstens@de.ibm.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] zfcp: kfree patch
Date: Mon, 10 Jan 2005 00:18:15 -0800	[thread overview]
Message-ID: <20050110081815.GA13612@kroah.com> (raw)
In-Reply-To: <OF21502B2A.CFA7983A-ONC1256F85.002AC44A-C1256F85.002CDDA7@de.ibm.com>

On Mon, Jan 10, 2005 at 09:10:21AM +0100, Heiko Carstens wrote:
> > > > As nothing has changed in the patch, I still object to it. Actually,
> > > > krefs will BUG() out if you try to do this, so I might as well add a
> > > > patch so that kobjects do the same thing...
> > > So what's the fix for this generic (non-zfcp specific) problem then?
> > As no other code uses this type of "solution" I don't see how you can
> > say it is "generic".
> 
> Since you still don't like the patch I would like to know how it should
> look like that you would accept it.

As I don't know the scsi subsystem, I can only rely on the fact that
kfree should never be used as a release call.  So fix that, and I'm
happy :)

> Also in my original post I described what the problem is. If that problem
> exists then it is generic.
> Please see also "Module unloading in a reference counted world"
> -> http://lwn.net/Articles/67421/

I understand the "generic" issue, however no other subsystem needs to
use kfree as a release call.  Now either everyone else is broken or...

thanks,

greg k-h

  reply	other threads:[~2005-01-10  8:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-08 10:36 [PATCH] zfcp: kfree patch Heiko Carstens
2005-01-08 11:44 ` Arjan van de Ven
2005-01-10  6:41   ` Heiko Carstens
2005-01-10 15:19     ` James Bottomley
2005-01-08 22:33 ` Greg KH
2005-01-10  6:53   ` Heiko Carstens
2005-01-10  7:06     ` Greg KH
2005-01-10  8:10       ` Heiko Carstens
2005-01-10  8:18         ` Greg KH [this message]
2005-01-10  9:27           ` Heiko Carstens
2005-01-12  6:47             ` Greg KH
2005-01-12  8:48               ` Heiko Carstens

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=20050110081815.GA13612@kroah.com \
    --to=greg@kroah.com \
    --cc=Heiko.Carstens@de.ibm.com \
    --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.