kobject_rename provides no locking. Signed-off-by: Peng Tao <bergwolf@xxxxxxxxx> --- Documentation/kobject.txt | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/kobject.txt b/Documentation/kobject.txt index f5d2aad..b6f7446 100644 --- a/Documentation/kobject.txt +++ b/Documentation/kobject.txt @@ -118,8 +118,8 @@ the name of the kobject, call kobject_rename(): int kobject_rename(struct kobject *kobj, const char *new_name); -Note kobject_rename does perform any locking or have a solid notion of -what names are valid so the provide must provide their own sanity checking +Note kobject_rename does not perform any locking or have a solid notion of +what names are valid so the provider must provide their own sanity checking and serialization. There is a function called kobject_set_name() but that is legacy cruft and -- 1.6.1.3 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html