Documentation/netlink/specs/lockd.yaml

Source file repositories/reference/linux-study-clean/Documentation/netlink/specs/lockd.yaml

File Facts

System: Linux kernel
Corpus path: Documentation/netlink/specs/lockd.yaml
Extension: .yaml
Size: 882 bytes
Lines: 46
Domain: Support Tooling And Documentation
Bucket: Documentation
Inferred role: Support Tooling And Documentation: configuration, schema, or hardware description
Status: atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
---
name: lockd
protocol: genetlink
uapi-header: linux/lockd_netlink.h

doc: lockd configuration over generic netlink

attribute-sets:
  -
    name: server
    attributes:
      -
        name: gracetime
        type: u32
      -
        name: tcp-port
        type: u16
      -
        name: udp-port
        type: u16

operations:
  list:
    -
      name: server-set
      doc: set the lockd server parameters
      attribute-set: server
      flags: [admin-perm]
      do:
        request:
          attributes:
            - gracetime
            - tcp-port
            - udp-port
    -
      name: server-get
      doc: get the lockd server parameters
      attribute-set: server
      do:
        reply:
          attributes:
            - gracetime
            - tcp-port
            - udp-port

Annotation

Atlas domain: Support Tooling And Documentation / Documentation.
Implementation status: atlas-only.

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.