Home
last modified time | relevance | path

Searched refs:buds (Results 1 – 5 of 5) sorted by relevance

/Linux-v5.4/fs/ubifs/
Dlog.c36 p = c->buds.rb_node; in ubifs_search_bud()
69 p = c->buds.rb_node; in ubifs_get_wbuf()
119 p = &c->buds.rb_node; in ubifs_add_bud()
131 rb_insert_color(&bud->rb, &c->buds); in ubifs_add_bud()
304 p = rb_first(&c->buds); in remove_buds()
329 rb_erase(p1, &c->buds); in remove_buds()
Ddebug.c620 for (rb = rb_first(&c->buds); rb; rb = rb_next(rb)) { in ubifs_dump_budg()
708 for (rb = rb_first((struct rb_root *)&c->buds); rb; rb = rb_next(rb)) { in ubifs_dump_lprop()
2525 } else if (write && !RB_EMPTY_ROOT(&c->buds) && in power_cut_emulated()
Dsuper.c896 rbtree_postorder_for_each_entry_safe(bud, n, &c->buds, rb) in free_buds()
2100 c->buds = RB_ROOT; in alloc_ubifs_info()
Dubifs.h1272 struct rb_root buds; member
/Linux-v5.4/Documentation/filesystems/
Dubifs-authentication.rst142 journal entry. These nodes are called *buds* and describe the actual filesystem
152 available to write the reference node and buds part of this entry. Then, the
153 reference node is written and afterwards the buds describing the file changes.
155 the referenced LEBs to discover the buds. If these are corrupt or missing,
179 containing their buds