Searched refs:garbage (Results 1 – 4 of 4) sorted by relevance
21 the garbage collector will obtain this right at the beginning of24 garbage collect pass.53 avoid deadlocks with garbage collection -- the VFS will lock the i_sem55 allocation may trigger garbage-collection, which may need to move a57 VFS. If the garbage collection code were to attempt to lock the i_sem58 of the inode from which it's garbage-collecting a physical node, this63 mutex, which is obtained by the garbage collection code and also97 pointer when the garbage collection thread exits. The code to kill the135 the jffs2_raw_node_ref structures in question while the garbage
24 By writing _new_ nodes to one block, and garbage-collected REF_PRISTINE
117 LIST_HEAD(garbage); in __kcore_update_ram()124 list_move(&pos->list, &garbage); in __kcore_update_ram()128 list_splice(list, &garbage); in __kcore_update_ram()133 free_kclist_ents(&garbage); in __kcore_update_ram()
587 char *garbage; in logfs_mount() local588 mtdnr = simple_strtoul(devname+3, &garbage, 0); in logfs_mount()589 if (*garbage) in logfs_mount()