Lines Matching refs:rmdir

28 mkdir(2).  It is destroyed via rmdir(2).  The attributes appear at
64 When an item needs to be destroyed, remove it with rmdir(2).  An
112 Items are created by mkdir(2) and removed by rmdir(2), but configfs
257 Finally, when userspace calls rmdir(2) on the item or group,
265 IMPORTANT: drop_item() is void, and as such cannot fail.  When rmdir(2)
284 is implemented in the configfs rmdir(2) code.  ->drop_item() will not be
285 called, as the item has not been dropped.  rmdir(2) will fail, as the
409 rmdir(2).  They also are not considered when rmdir(2) on the parent
416 region item is removed with rmdir(2), the ocfs2 mount must BUG or go
422 depended on.  configfs will then return -EBUSY from rmdir(2) for that
471 support mkdir(2) or rmdir(2) either.  It only allows rename(2).  The
472 "pending" directory does allow mkdir(2) and rmdir(2).  An item is
479 As rmdir(2) does not work in the "live" directory, an item must be