fs/notify/mark.c
Source file repositories/reference/linux-study-clean/fs/notify/mark.c
File Facts
- System
- Linux kernel
- Corpus path
fs/notify/mark.c- Extension
.c- Size
- 35416 bytes
- Lines
- 1195
- Domain
- Core OS
- Bucket
- VFS And Filesystem Core
- Inferred role
- Core OS: exported/initcall integration point
- Status
- integration implementation candidate
Why This File Exists
Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/fs.hlinux/init.hlinux/kernel.hlinux/kthread.hlinux/module.hlinux/mutex.hlinux/slab.hlinux/spinlock.hlinux/srcu.hlinux/ratelimit.hlinux/atomic.hlinux/fsnotify_backend.hfsnotify.h
Detected Declarations
struct fsnotify_inode_mark_connectorfunction fsnotify_get_markfunction fsnotify_conn_maskfunction fsnotify_get_sb_watched_objectsfunction fsnotify_put_sb_watched_objectsfunction fsnotify_get_inode_reffunction fsnotify_put_inode_reffunction fsnotify_update_sb_watchersfunction iputfunction __fsnotify_recalc_maskfunction __fsnotify_recalc_maskfunction fsnotify_conn_watches_childrenfunction fsnotify_conn_set_children_dentry_flagsfunction fsnotify_recalc_maskfunction fsnotify_modify_mark_maskfunction fsnotify_connector_destroy_workfnfunction fsnotify_final_mark_destroyfunction fsnotify_drop_objectfunction fsnotify_put_markfunction fsnotify_get_mark_safefunction fsnotify_get_mark_safefunction fsnotify_prepare_user_waitfunction fsnotify_foreach_iter_typefunction fsnotify_finish_user_waitfunction fsnotify_detach_markfunction fsnotify_free_markfunction fsnotify_destroy_markfunction classesfunction fsnotify_attach_info_to_sbfunction cmpxchgfunction fsnotify_unmount_inodesfunction fsnotify_init_connectorfunction fsnotify_alloc_inode_connectorfunction fsnotify_untrack_connectorfunction fsnotify_attach_connector_to_objectfunction cmpxchgfunction fsnotify_add_mark_listfunction fsnotify_add_mark_lockedfunction fsnotify_add_markfunction hlist_for_each_entryfunction fsnotify_clear_marks_by_groupfunction fsnotify_destroy_marksfunction fsnotify_clear_marks_by_groupfunction fsnotify_init_markfunction fsnotify_mark_destroy_workfnfunction list_for_each_entry_safefunction fsnotify_wait_marks_destroyedfunction fsnotify_init_connector_caches
Annotated Snippet
struct fsnotify_inode_mark_connector {
struct fsnotify_mark_connector common;
struct list_head conns_list;
};
static struct inode *fsnotify_get_living_inode(struct fsnotify_sb_info *sbinfo)
{
struct fsnotify_inode_mark_connector *iconn;
struct inode *inode;
spin_lock(&sbinfo->list_lock);
/* Find the first non-evicting inode */
list_for_each_entry(iconn, &sbinfo->inode_conn_list, conns_list) {
/* All connectors on the list are still attached to an inode */
inode = iconn->common.obj;
/*
* For connectors without FSNOTIFY_CONN_FLAG_HAS_IREF
* (evictable marks) corresponding inode may well have 0
* refcount and can be undergoing eviction. OTOH list_lock
* protects us from the connector getting detached and inode
* freed. So we can poke around the inode safely.
*/
spin_lock(&inode->i_lock);
if (likely(
!(inode_state_read(inode) & (I_FREEING | I_WILL_FREE)))) {
__iget(inode);
spin_unlock(&inode->i_lock);
spin_unlock(&sbinfo->list_lock);
return inode;
}
spin_unlock(&inode->i_lock);
}
spin_unlock(&sbinfo->list_lock);
return NULL;
}
/**
* fsnotify_unmount_inodes - an sb is unmounting. Handle any watched inodes.
* @sbinfo: fsnotify info for superblock being unmounted.
*
* Walk all inode connectors for the superblock and free all associated marks.
*/
void fsnotify_unmount_inodes(struct fsnotify_sb_info *sbinfo)
{
struct inode *inode;
while ((inode = fsnotify_get_living_inode(sbinfo))) {
fsnotify_inode(inode, FS_UNMOUNT);
fsnotify_clear_marks_by_inode(inode);
iput(inode);
cond_resched();
}
}
static void fsnotify_init_connector(struct fsnotify_mark_connector *conn,
void *obj, unsigned int obj_type)
{
spin_lock_init(&conn->lock);
INIT_HLIST_HEAD(&conn->list);
conn->flags = 0;
conn->prio = 0;
conn->type = obj_type;
conn->obj = obj;
}
static struct fsnotify_mark_connector *
fsnotify_alloc_inode_connector(struct inode *inode)
{
struct fsnotify_inode_mark_connector *iconn;
struct fsnotify_sb_info *sbinfo = fsnotify_sb_info(inode->i_sb);
iconn = kmem_cache_alloc(fsnotify_inode_mark_connector_cachep,
GFP_KERNEL);
if (!iconn)
return NULL;
fsnotify_init_connector(&iconn->common, inode, FSNOTIFY_OBJ_TYPE_INODE);
spin_lock(&sbinfo->list_lock);
list_add(&iconn->conns_list, &sbinfo->inode_conn_list);
spin_unlock(&sbinfo->list_lock);
return &iconn->common;
}
static void fsnotify_untrack_connector(struct fsnotify_mark_connector *conn)
{
struct fsnotify_inode_mark_connector *iconn;
struct fsnotify_sb_info *sbinfo;
Annotation
- Immediate include surface: `linux/fs.h`, `linux/init.h`, `linux/kernel.h`, `linux/kthread.h`, `linux/module.h`, `linux/mutex.h`, `linux/slab.h`, `linux/spinlock.h`.
- Detected declarations: `struct fsnotify_inode_mark_connector`, `function fsnotify_get_mark`, `function fsnotify_conn_mask`, `function fsnotify_get_sb_watched_objects`, `function fsnotify_put_sb_watched_objects`, `function fsnotify_get_inode_ref`, `function fsnotify_put_inode_ref`, `function fsnotify_update_sb_watchers`, `function iput`, `function __fsnotify_recalc_mask`.
- Atlas domain: Core OS / VFS And Filesystem Core.
- Implementation status: integration implementation candidate.
- Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.