Lines Matching full:item
49 These are modules that register their item types with configfs as
54 An item is created via mkdir(2). The item's attributes will also
71 apply, but the whole binary item must fit in single kernel vmalloc'ed buffer.
79 When an item needs to be destroyed, remove it with rmdir(2). An
80 item cannot be destroyed if any other item has a link to it (via
176 Usually a subsystem wants the item to display and/or store attributes,
219 When a config_item wants an attribute to appear as a file in the item's
222 config_item_type->ct_attrs. When the item appears in configfs, the
243 appear as the contents of a file in the item's configfs directory.
245 config_item_type->ct_bin_attrs, and the item appears in configfs, the
265 child item::
282 that item means that a group can behave as an item in its own right.
292 int (*commit_item)(struct config_item *item);
294 struct config_item *item);
296 struct config_item *item);
304 tree to reflect the new item.
310 Finally, when userspace calls rmdir(2) on the item or group,
314 upon item allocation. If a subsystem has no work to do, it may omit
316 config_item_put() on the item on behalf of the subsystem.
320 is called, configfs WILL remove the item from the filesystem tree
323 the item in other threads, the memory is safe. It may take some time
324 for the item to actually disappear from the subsystem's usage. But it
327 When drop_item() is called, the item's linkage has already been torn
329 the item hierarchy. If a client needs to do some cleanup before this
332 configfs has removed the item from the filesystem view but before the
333 item is removed from its parent group. Like drop_item(),
339 called, as the item has not been dropped. rmdir(2) will fail, as the
371 subsystem/group and the simple_child item in
394 allocated item has not been linked into this hierarchy. Similarly, it
395 will not be able to acquire the mutex while a dropping item has not
396 yet been unlinked. This means that an item's ci_parent pointer will
397 never be NULL while the item is in configfs, and that an item will only
402 Item Aggregation Via symlink(2)
405 configfs provides a simple group via the group->item parent/child
417 method is called with itself and a target item. If the source item
418 allows linking to target item, it returns 0. A source item may wish to
422 When unlink(2) is called on the symbolic link, the source item is
427 A config_item cannot be removed while it links to any other item, nor
428 can it be removed while an item links to it. Dangling symlinks are not
466 example, ocfs2 mounts depend on a heartbeat region item. If that
467 region item is removed with rmdir(2), the ocfs2 mount must BUG or go
472 configfs_depend_item() on an existing item to tell configfs that it is
474 item. When the item is no longer depended on, the client driver calls
483 it asks for a heartbeat region item. This is done via a call into the
484 heartbeat code. Inside the heartbeat code, the region item is looked
497 default values can be specified for the item's attributes such that the
498 item can do its work. Userspace must configure one or more attributes,
499 after which the subsystem can start whatever entity this item
516 configfs still uses only normal filesystem operations. An item is
517 committed via rename(2). The item is moved from a directory where it
525 "pending" directory does allow mkdir(2) and rmdir(2). An item is
527 will. Userspace commits the item by renaming it into the "live"
530 method returns zero and the item is moved to the "live" directory.
532 As rmdir(2) does not work in the "live" directory, an item must be