From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: mochel@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: Ref-count problem in kset_find_obj?
Date: Wed, 29 Oct 2003 13:38:20 +0100 [thread overview]
Message-ID: <20031029123820.GA1141@mschwid3.boeblingen.de.ibm.com> (raw)
Hi Pat,
looking through the sysfs code I noticed a potential problem in
kset_find_obj:
struct kobject * kset_find_obj(struct kset * kset, const char * name)
{
struct list_head * entry;
struct kobject * ret = NULL;
down_read(&kset->subsys->rwsem);
list_for_each(entry,&kset->list) {
struct kobject * k = to_kobj(entry);
if (!strcmp(kobject_name(k),name)) {
ret = k;
break;
}
}
up_read(&kset->subsys->rwsem);
return ret;
}
The reference count of the kobject to be returned is not
increased before the semaphore is released. A kobject_del/unlink
could remove the object before the called of kset_find_obj is
able to increase the reference count. This makes kset_find_obj
more or less unusable, doesn't it?
blue skies,
Martin.
next reply other threads:[~2003-10-29 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 12:38 Martin Schwidefsky [this message]
2003-10-30 0:24 ` Patrick Mochel
2003-10-30 5:42 ` Matt Domsch
2003-10-30 8:46 Martin Schwidefsky
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=20031029123820.GA1141@mschwid3.boeblingen.de.ibm.com \
--to=schwidefsky@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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
Powered by JetHome