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,
192 When a config_item wants an attribute to appear as a file in the item's
195 config_item_type->ct_attrs.  When the item appears in configfs, the
208 child item.
224 that item means that a group can behave as an item in its own right.
234 		int (*commit_item)(struct config_item *item);
236 					  struct config_item *item);
238 				  struct config_item *item);
245 tree to reflect the new item.
251 Finally, when userspace calls rmdir(2) on the item or group,
255 upon item allocation.  If a subsystem has no work to do, it may omit
257 config_item_put() on the item on behalf of the subsystem.
260 is called, configfs WILL remove the item from the filesystem tree
263 the item in other threads, the memory is safe.  It may take some time
264 for the item to actually disappear from the subsystem's usage.  But it
267 When drop_item() is called, the item's linkage has already been torn
269 the item hierarchy.  If a client needs to do some cleanup before this
272 configfs has removed the item from the filesystem view but before the
273 item is removed from its parent group.  Like drop_item(),
279 called, as the item has not been dropped.  rmdir(2) will fail, as the
308 subsystem/group and the simple_child item in
330 allocated item has not been linked into this hierarchy.   Similarly, it
331 will not be able to acquire the mutex while a dropping item has not
332 yet been unlinked.  This means that an item's ci_parent pointer will
333 never be NULL while the item is in configfs, and that an item will only
340 configfs provides a simple group via the group->item parent/child
352 method is called with itself and a target item.  If the source item
353 allows linking to target item, it returns 0.  A source item may wish to
357 When unlink(2) is called on the symbolic link, the source item is
362 A config_item cannot be removed while it links to any other item, nor
363 can it be removed while an item links to it.  Dangling symlinks are not
399 example, ocfs2 mounts depend on a heartbeat region item.  If that
400 region item is removed with rmdir(2), the ocfs2 mount must BUG or go
405 configfs_depend_item() on an existing item to tell configfs that it is
407 item.  When the item is no longer depended on, the client driver calls
416 it asks for a heartbeat region item.  This is done via a call into the
417 heartbeat code.  Inside the heartbeat code, the region item is looked
428 default values can be specified for the item's attributes such that the
429 item can do its work.  Userspace must configure one or more attributes,
430 after which the subsystem can start whatever entity this item
447 configfs still uses only normal filesystem operations.  An item is
448 committed via rename(2).  The item is moved from a directory where it
456 "pending" directory does allow mkdir(2) and rmdir(2).  An item is
458 will.  Userspace commits the item by renaming it into the "live"
461 method returns zero and the item is moved to the "live" directory.
463 As rmdir(2) does not work in the "live" directory, an item must be