evict_should_delete(9)
π evict_should_delete(9) β the Kernel API Manual tea β
Okay bestie, so this one lives in the Kernel API Manual and it's called evict_should_delete. Yes, it's exactly as dramatic as it sounds β we're doing a vibe check on an inode to see if it's β¨eligible for deletionβ¨.
πΈ NAME πΈ
evict_should_delete β determine whether the inode is eligible for deletion
Like, the whole point. That's the assignment. π―
β¨ SYNOPSIS β¨
enum evict_behavior evict_should_delete (struct inode *inode , struct gfs2_holder *gh );
Copy it exactly, okay? Don't come for me, this is verbatim fr fr. π«Ά
π ARGUMENTS π
inodeβ The inode to evict. This is the main character of the whole operation, ngl.ghβ The glock holder structure. The supporting cast, but lowkey essential. π
π¦ DESCRIPTION π¦
So this function determines whether the evicted inode is eligible to be deleted, and β plot twist β it also locks the inode glock. Two jobs, one function, main character energy honestly. π
π RETURN π
It returns the fate of the dinode. Yep. The fate. Very dramatic. Destiny but make it a return value. π₯
π SEE ALSO π
Kernel file ./fs/gfs2/super.c β and the whole friend group:
gfs2_jindex_free(9)gfs2_make_fs_rw(9)gfs2_lock_fs_check_clean(9)gfs2_write_inode(9)gfs2_dirty_inode(9)gfs2_make_fs_ro(9)gfs2_put_super(9)gfs2_sync_fs(9)gfs2_freeze_super(9)gfs2_thaw_super(9)statfs_slow_fill(9)gfs2_statfs_slow(9)gfs2_statfs_i(9)gfs2_statfs(9)gfs2_drop_inode(9)gfs2_show_options(9)gfs2_glock_put_eventually(9)evict_unlinked_inode(9)gfs2_evict_inode(9)
Read them all, bestie. For the lore. πβ¨
No cap, that's every single reference β didn't skip a one. Your faves are all here. π«Ά
And that's the page, babe! Written by the ./fs/gfs2 girlies, dated October 2026 β yeah, they're from the future, and they still said evict_should_delete(9) at the bottom. Slay. πππ«
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms