fs/gfs2/recovery.h

File Facts

System

Linux kernel

Corpus path

fs/gfs2/recovery.h

Extension

.h

Size

1131 bytes

Lines

37

Domain

Core OS

Bucket

VFS And Filesystem Core

Inferred role

Core OS: implementation source

Status

source 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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• incore.h

Detected Declarations

• function gfs2_replay_incr_blk

Annotated Snippet

#ifndef __RECOVERY_DOT_H__
#define __RECOVERY_DOT_H__

#include "incore.h"

extern struct workqueue_struct *gfs2_recovery_wq;

static inline void gfs2_replay_incr_blk(struct gfs2_jdesc *jd, u32 *blk)
{
	if (++*blk == jd->jd_blocks)
	        *blk = 0;
}

int gfs2_replay_read_block(struct gfs2_jdesc *jd, unsigned int blk,
			   struct buffer_head **bh);

int gfs2_revoke_add(struct gfs2_jdesc *jd, u64 blkno, unsigned int where);
int gfs2_revoke_check(struct gfs2_jdesc *jd, u64 blkno, unsigned int where);
void gfs2_revoke_clean(struct gfs2_jdesc *jd);

int gfs2_recover_journal(struct gfs2_jdesc *gfs2_jd, bool wait);
void gfs2_recover_func(struct work_struct *work);
int __get_log_header(struct gfs2_sbd *sdp,
		     const struct gfs2_log_header *lh, unsigned int blkno,
		     struct gfs2_log_header_host *head);
void gfs2_log_pointers_init(struct gfs2_sbd *sdp,
			    struct gfs2_log_header_host *head);

#endif /* __RECOVERY_DOT_H__ */

Annotation

• Immediate include surface: `incore.h`.
• Detected declarations: `function gfs2_replay_incr_blk`.
• Atlas domain: Core OS / VFS And Filesystem Core.
• Implementation status: source implementation candidate.

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.