All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Akinobu Mita <mita@miraclelinux.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [patch 1/4] kref: warn kref_put() with unreferenced kref
Date: Thu, 27 Apr 2006 13:45:12 +0200	[thread overview]
Message-ID: <20060427114512.GA6533@bitwizard.nl> (raw)
In-Reply-To: <20060424083341.613638000@localhost.localdomain>

On Mon, Apr 24, 2006 at 04:33:34PM +0800, Akinobu Mita wrote:
> @@ -56,12 +57,13 @@ int kref_put(struct kref *kref, void (*r
>  	 * if current count is one, we are the last user and can release object
>  	 * right now, avoiding an atomic operation on 'refcount'
>  	 */
> -	if ((atomic_read(&kref->refcount) == 1) ||
> -	    (atomic_dec_and_test(&kref->refcount))) {
> -		release(kref);
> -		return 1;
> -	}
> -	return 0;
> +	if (atomic_read(&kref->refcount) == 1)
> +		atomic_set(&kref->refcount, 0);
> +	else if (!atomic_dec_and_test(&kref->refcount))
> +		return 0;

This is WRONG. The refcount can be incremented (to two) AFTER the
atomic_read ==1 and the "atomic_set". The original code seems 
ok in this respect. 

	Roger. 


-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement. 
Does it sit on the couch all day? Is it unemployed? Please be specific! 
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ

  parent reply	other threads:[~2006-04-27 11:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-24  8:33 [patch 0/4] kref debugging Akinobu Mita
2006-04-24  8:33 ` [patch 1/4] kref: warn kref_put() with unreferenced kref Akinobu Mita
2006-04-25  3:51   ` Greg KH
2006-04-25  4:19     ` Valdis.Kletnieks
2006-04-25  5:11       ` Greg KH
2006-04-25  4:34     ` Akinobu Mita
2006-04-25  5:09       ` Greg KH
2006-04-25  6:27         ` Akinobu Mita
2006-04-27 11:45   ` Rogier Wolff [this message]
2006-04-24  8:33 ` [patch 2/4] kref debugging config option Akinobu Mita
2006-04-24 21:38   ` Andrew Morton
2006-04-25  4:53     ` Akinobu Mita
2006-04-25  5:08       ` Greg KH
2006-04-25  3:52   ` Greg KH
2006-04-24  8:33 ` [patch 3/4] dynamic configurable kref debugging Akinobu Mita
2006-04-25  3:55   ` Greg KH
2006-04-24  8:33 ` [patch 4/4] change slab poison pattern Akinobu Mita
2006-04-24  9:20   ` Pekka Enberg
2006-04-24 10:23     ` Akinobu Mita
2006-04-24 15:33       ` Matt Mackall
2006-04-25  3:49 ` [patch 0/4] kref debugging 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=20060427114512.GA6533@bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mita@miraclelinux.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 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.