Finally, when userspace calls rmdir(2) on the item or group,
ct_group_ops->drop_item() is called. As a config_group is also a
Finally, when userspace calls rmdir(2) on the item or group,
ct_group_ops->drop_item() is called. As a config_group is also a
The subsystem must config_item_put() the reference that was initialized
upon item allocation. If a subsystem has no work to do, it may omit
the ct_group_ops->drop_item() method, and configfs will call
The subsystem must config_item_put() the reference that was initialized
upon item allocation. If a subsystem has no work to do, it may omit
the ct_group_ops->drop_item() method, and configfs will call
Far better would be an explicit action notifying the subsystem that the
config_item is ready to go. More importantly, an explicit action allows
Far better would be an explicit action notifying the subsystem that the
config_item is ready to go. More importantly, an explicit action allows
"pending" directory does allow mkdir(2) and rmdir(2). An item is
created in the "pending" directory. Its attributes can be modified at
will. Userspace commits the item by renaming it into the "live"
"pending" directory does allow mkdir(2) and rmdir(2). An item is
created in the "pending" directory. Its attributes can be modified at
will. Userspace commits the item by renaming it into the "live"
callback. If all required attributes are filled to satisfaction, the
method returns zero and the item is moved to the "live" directory.
callback. If all required attributes are filled to satisfaction, the
method returns zero and the item is moved to the "live" directory.