fs/fuse/virtio_fs.c

File Facts

System

Linux kernel

Corpus path

fs/fuse/virtio_fs.c

Extension

.c

Size

45644 bytes

Lines

1856

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• 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.h
• linux/dax.h
• linux/pci.h
• linux/interrupt.h
• linux/group_cpus.h
• linux/memremap.h
• linux/module.h
• linux/virtio.h
• linux/virtio_fs.h
• linux/delay.h
• linux/fs_context.h
• linux/fs_parser.h
• linux/highmem.h
• linux/cleanup.h
• linux/uio.h
• dev.h
• fuse_i.h
• fuse_dev_i.h

Detected Declarations

• struct virtio_fs_vq
• struct virtio_fs
• struct virtio_fs_forget_req
• struct virtio_fs_forget
• struct virtio_fs_req_work
• function virtio_fs_parse_param
• function virtio_fs_free_fsc
• function inc_in_flight_req
• function dec_in_flight_req
• function tag_show
• function virtio_fs_ktype_release
• function name_show
• function cpu_list_show
• function virtio_fs_put_locked
• function virtio_fs_put
• function virtio_fs_fiq_release
• function virtio_fs_drain_queue
• function virtio_fs_drain_all_queues_locked
• function virtio_fs_drain_all_queues
• function virtio_fs_start_all_queues
• function virtio_fs_delete_queues_sysfs
• function virtio_fs_add_queues_sysfs
• function virtio_fs_add_instance
• function list_for_each_entry
• function list_for_each_entry
• function virtio_fs_free_devs
• function virtio_fs_read_tag
• function mount
• function virtio_fs_hiprio_done_work
• function virtio_fs_request_dispatch_work
• function send_forget_request
• function virtio_fs_hiprio_dispatch_work
• function copy_args_to_argbuf
• function copy_args_from_argbuf
• function virtio_fs_verify_response
• function virtio_fs_request_complete
• function virtio_fs_complete_req_work
• function virtio_fs_requests_done_work
• function virtio_fs_map_queues
• function virtio_fs_vq_done
• function virtio_fs_init_vq
• function virtio_fs_setup_vqs
• function virtio_fs_cleanup_vqs
• function virtio_fs_direct_access
• function virtio_fs_zero_page_range
• function virtio_fs_cleanup_dax
• function virtio_fs_setup_dax
• function devm_memremap_pages

Annotated Snippet

module_init(virtio_fs_init);

static void __exit virtio_fs_exit(void)
{
	unregister_filesystem(&virtio_fs_type);
	unregister_virtio_driver(&virtio_fs_driver);
	virtio_fs_sysfs_exit();
}
module_exit(virtio_fs_exit);

MODULE_AUTHOR("Stefan Hajnoczi <stefanha@redhat.com>");
MODULE_DESCRIPTION("Virtio Filesystem");
MODULE_LICENSE("GPL");
MODULE_ALIAS_FS(KBUILD_MODNAME);
MODULE_DEVICE_TABLE(virtio, id_table);

Annotation

• Immediate include surface: `linux/fs.h`, `linux/dax.h`, `linux/pci.h`, `linux/interrupt.h`, `linux/group_cpus.h`, `linux/memremap.h`, `linux/module.h`, `linux/virtio.h`.
• Detected declarations: `struct virtio_fs_vq`, `struct virtio_fs`, `struct virtio_fs_forget_req`, `struct virtio_fs_forget`, `struct virtio_fs_req_work`, `function virtio_fs_parse_param`, `function virtio_fs_free_fsc`, `function inc_in_flight_req`, `function dec_in_flight_req`, `function tag_show`.
• 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.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.