Open yuheho7749 opened 6 days ago
That could be used for small truncates, but I also have __free_{single,double,triple}_indirect_blk
helper functions to remove larger chunks on my development branch.
Rather, the remove_dblk will be really useful for deleting a directory entry where it at most frees one blk.
Sure. Great! I planned to write a large range remove (like remove all dblks after a start_index), but seems you will use several more fine controlled helpers, so I will postpone writing that. (Tell me if you really need it).
I'm working on remove_dblk_no_from_inode() (including indirect blocks), which may support your truncate().