From: Greg KH <gregkh@linuxfoundation.org>
To: Anatol Pomozov <anatol.pomozov@gmail.com>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: [PATCH] kref: minor cleanup
Date: Fri, 19 Apr 2013 19:24:15 -0700 [thread overview]
Message-ID: <20130420022415.GA24713@kroah.com> (raw)
In-Reply-To: <1366421634-20773-1-git-send-email-anatol.pomozov@gmail.com>
On Fri, Apr 19, 2013 at 06:33:54PM -0700, Anatol Pomozov wrote:
> Follow-up for https://lkml.org/lkml/2013/4/12/391
>
> * make warning smp-safe
> * result of atomic _unless_zero functions should be checked by caller
> to avoid use-after-free error
>
> Signed-off-by: Anatol Pomozov <anatol.pomozov@gmail.com>
> ---
> include/linux/kref.h | 9 ++++++---
> lib/kobject.c | 3 ++-
> 2 files changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/include/linux/kref.h b/include/linux/kref.h
> index 4972e6e..092529a 100644
> --- a/include/linux/kref.h
> +++ b/include/linux/kref.h
> @@ -39,8 +39,11 @@ static inline void kref_init(struct kref *kref)
> */
> static inline void kref_get(struct kref *kref)
> {
> - WARN_ON(!atomic_read(&kref->refcount));
> - atomic_inc(&kref->refcount);
> + /* If refcount was 0 before incrementing then we have a race
> + * condition when this kref is freing by some other thread right now.
> + * In this case one should use kref_get_unless_zero()
> + */
> + WARN_ON(atomic_inc_return(&kref->refcount) < 2);
What happens if you disable WARN_ON(), does the atomic_inc_return() go
away as well? Or did we fix that?
> }
>
> /**
> @@ -100,7 +103,7 @@ static inline int kref_put_mutex(struct kref *kref,
> struct mutex *lock)
> {
> WARN_ON(release == NULL);
> - if (unlikely(!atomic_add_unless(&kref->refcount, -1, 1))) {
> + if (unlikely(!atomic_add_unless(&kref->refcount, -1, 1))) {
> mutex_lock(lock);
> if (unlikely(!atomic_dec_and_test(&kref->refcount))) {
> mutex_unlock(lock);
> diff --git a/lib/kobject.c b/lib/kobject.c
> index a654866..bbd7362 100644
> --- a/lib/kobject.c
> +++ b/lib/kobject.c
> @@ -529,7 +529,8 @@ struct kobject *kobject_get(struct kobject *kobj)
> return kobj;
> }
>
> -static struct kobject *kobject_get_unless_zero(struct kobject *kobj)
> +static struct kobject *__must_check kobject_get_unless_zero(
> + struct kobject *kobj)
__must_check needs to be in the .h file, not the .c file.
thanks,
greg k-h
next prev parent reply other threads:[~2013-04-20 2:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 1:33 [PATCH] kref: minor cleanup Anatol Pomozov
2013-04-20 2:24 ` Greg KH [this message]
2013-04-20 4:27 ` Anatol Pomozov
2013-04-20 22:31 ` Greg KH
2013-04-20 16:15 ` Anatol Pomozov
2013-04-20 22:34 ` Greg KH
2013-04-25 1:38 ` Anatol Pomozov
-- strict thread matches above, loose matches on Subject: below --
2013-05-07 22:37 Anatol Pomozov
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=20130420022415.GA24713@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=anatol.pomozov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox