Lines Matching refs:item

46 These are modules that register their item types with configfs as
51 An item is created via mkdir(2).  The item's attributes will also
64 When an item needs to be destroyed, remove it with rmdir(2).  An
65 item cannot be destroyed if any other item has a link to it (via
156 Usually a subsystem wants the item to display and/or store attributes,
198 When a config_item wants an attribute to appear as a file in the item's
201 config_item_type->ct_attrs.  When the item appears in configfs, the
214 child item.
230 that item means that a group can behave as an item in its own right.
240 		int (*commit_item)(struct config_item *item);
242 					  struct config_item *item);
244 				  struct config_item *item);
251 tree to reflect the new item.
257 Finally, when userspace calls rmdir(2) on the item or group,
261 upon item allocation.  If a subsystem has no work to do, it may omit
263 config_item_put() on the item on behalf of the subsystem.
266 is called, configfs WILL remove the item from the filesystem tree
269 the item in other threads, the memory is safe.  It may take some time
270 for the item to actually disappear from the subsystem's usage.  But it
273 When drop_item() is called, the item's linkage has already been torn
275 the item hierarchy.  If a client needs to do some cleanup before this
278 configfs has removed the item from the filesystem view but before the
279 item is removed from its parent group.  Like drop_item(),
285 called, as the item has not been dropped.  rmdir(2) will fail, as the
314 subsystem/group and the simple_child item in configfs_example_explicit.c
320 configfs_example_macros.c is how the attributes of the childless item
321 are defined.  The childless item has extended attributes, each with
346 allocated item has not been linked into this hierarchy.   Similarly, it
347 will not be able to acquire the mutex while a dropping item has not
348 yet been unlinked.  This means that an item's ci_parent pointer will
349 never be NULL while the item is in configfs, and that an item will only
356 configfs provides a simple group via the group->item parent/child
368 method is called with itself and a target item.  If the source item
369 allows linking to target item, it returns 0.  A source item may wish to
373 When unlink(2) is called on the symbolic link, the source item is
378 A config_item cannot be removed while it links to any other item, nor
379 can it be removed while an item links to it.  Dangling symlinks are not
415 example, ocfs2 mounts depend on a heartbeat region item.  If that
416 region item is removed with rmdir(2), the ocfs2 mount must BUG or go
421 configfs_depend_item() on an existing item to tell configfs that it is
423 item.  When the item is no longer depended on, the client driver calls
432 it asks for a heartbeat region item.  This is done via a call into the
433 heartbeat code.  Inside the heartbeat code, the region item is looked
444 default values can be specified for the item's attributes such that the
445 item can do its work.  Userspace must configure one or more attributes,
446 after which the subsystem can start whatever entity this item
463 configfs still uses only normal filesystem operations.  An item is
464 committed via rename(2).  The item is moved from a directory where it
472 "pending" directory does allow mkdir(2) and rmdir(2).  An item is
474 will.  Userspace commits the item by renaming it into the "live"
477 method returns zero and the item is moved to the "live" directory.
479 As rmdir(2) does not work in the "live" directory, an item must be