fs/jbd2/journal.c

File Facts

System

Linux kernel

Corpus path

fs/jbd2/journal.c

Extension

.c

Size

89094 bytes

Lines

3066

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/module.h
• linux/time.h
• linux/fs.h
• linux/jbd2.h
• linux/errno.h
• linux/slab.h
• linux/init.h
• linux/mm.h
• linux/freezer.h
• linux/pagemap.h
• linux/kthread.h
• linux/poison.h
• linux/proc_fs.h
• linux/seq_file.h
• linux/math64.h
• linux/hash.h
• linux/log2.h
• linux/vmalloc.h
• linux/backing-dev.h
• linux/bitops.h
• linux/ratelimit.h
• linux/sched/mm.h
• trace/events/jbd2.h
• linux/uaccess.h
• asm/page.h

Detected Declarations

• struct jbd2_stats_proc_session
• function __jbd2_debug
• function jbd2_superblock_csum
• function commit_timeout
• function kjournald2
• function jbd2_journal_start_thread
• function journal_kill_thread
• function jbd2_data_needs_escaping
• function jbd2_data_do_escape
• function jbd2_journal_write_metadata_buffer
• function __jbd2_log_start_commit
• function transaction
• function jbd2_log_start_commit
• function __jbd2_journal_force_commit
• function jbd2_journal_force_commit_nested
• function jbd2_journal_force_commit
• function transaction
• function jbd2_trans_will_send_data_barrier
• function jbd2_log_wait_commit
• function jbd2_fc_begin_commit
• function __jbd2_fc_end_commit
• function jbd2_fc_end_commit
• function jbd2_fc_end_commit_fallback
• function jbd2_transaction_committed
• function jbd2_complete_transaction
• function jbd2_journal_next_log_block
• function jbd2_fc_get_buf
• function jbd2_fc_wait_bufs
• function jbd2_fc_release_bufs
• function jbd2_journal_bmap
• function jbd2_journal_get_descriptor_buffer
• function jbd2_descriptor_block_csum_set
• function jbd2_journal_get_log_tail
• function valid
• function jbd2_update_log_tail
• function jbd2_seq_info_show
• function jbd2_seq_info_stop
• function jbd2_seq_info_open
• function jbd2_seq_info_release
• function jbd2_stats_proc_init
• function jbd2_stats_proc_exit
• function jbd2_min_tag_size
• function jbd2_journal_shrink_scan
• function jbd2_journal_shrink_count
• function journal_fail_superblock
• function journal_check_superblock
• function be32_to_cpu
• function journal_revoke_records_per_block

Annotated Snippet

module_init(journal_init);
module_exit(journal_exit);

Annotation

• Immediate include surface: `linux/module.h`, `linux/time.h`, `linux/fs.h`, `linux/jbd2.h`, `linux/errno.h`, `linux/slab.h`, `linux/init.h`, `linux/mm.h`.
• Detected declarations: `struct jbd2_stats_proc_session`, `function __jbd2_debug`, `function jbd2_superblock_csum`, `function commit_timeout`, `function kjournald2`, `function jbd2_journal_start_thread`, `function journal_kill_thread`, `function jbd2_data_needs_escaping`, `function jbd2_data_do_escape`, `function jbd2_journal_write_metadata_buffer`.
• 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.