[<prev] [next>] [day] [month] [year] [list]
Message-Id: <201012211309.23159.bvanassche@acm.org>
Date: Tue, 21 Dec 2010 13:09:23 +0100
From: Bart Van Assche <bvanassche@....org>
To: linux-kernel@...r.kernel.org
Cc: "Greg Kroah-Hartman" <gregkh@...e.de>, Tejun Heo <tj@...nel.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>
Subject: [PATCH 1/2] docs/sysfs: Update directory/kobject documentation.
Some time ago the way how sysfs stores a pointer to a kobject
corresponding to a directory was modified. This patch brings the
documentation again in sync with the implementation.
Signed-off-by: Bart Van Assche <bvanassche@....org>
Cc: Greg KH <greg@...ah.com>
Cc: Tejun Heo <tj@...nel.org>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>
---
Documentation/filesystems/sysfs.txt | 10 ++++++----
1 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/Documentation/filesystems/sysfs.txt b/Documentation/filesystems/sysfs.txt
index 5d1335f..2ed95f9 100644
--- a/Documentation/filesystems/sysfs.txt
+++ b/Documentation/filesystems/sysfs.txt
@@ -39,10 +39,12 @@ userspace. Top-level directories in sysfs represent the common
ancestors of object hierarchies; i.e. the subsystems the objects
belong to.
-Sysfs internally stores the kobject that owns the directory in the
-->d_fsdata pointer of the directory's dentry. This allows sysfs to do
-reference counting directly on the kobject when the file is opened and
-closed.
+Sysfs internally stores a pointer to the kobject that implements a
+directory in the sysfs_dirent object associated with the directory. In
+the past this kobject pointer has been used by sysfs to do reference
+counting directly on the kobject whenever the file is opened or closed.
+With the current sysfs implementation the kobject reference count is
+only modified directly by the function sysfs_schedule_callback().
Attributes
--
1.7.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists