net/batman-adv/log.c
Source file repositories/reference/linux-study-clean/net/batman-adv/log.c
File Facts
- System
- Linux kernel
- Corpus path
net/batman-adv/log.c- Extension
.c- Size
- 637 bytes
- Lines
- 37
- Domain
- Networking Core
- Bucket
- Sockets, Protocols, Packet Path, And Network Policy
- Inferred role
- Networking Core: implementation source
- Status
- source implementation candidate
Why This File Exists
Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.
- Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
log.hmain.hlinux/stdarg.htrace.h
Detected Declarations
function batadv_debug_log
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/* Copyright (C) B.A.T.M.A.N. contributors:
*
* Marek Lindner
*/
#include "log.h"
#include "main.h"
#include <linux/stdarg.h>
#include "trace.h"
/**
* batadv_debug_log() - Add debug log entry
* @bat_priv: the bat priv with all the mesh interface information
* @fmt: format string
*
* Return: 0 on success or negative error number in case of failure
*/
int batadv_debug_log(struct batadv_priv *bat_priv, const char *fmt, ...)
{
struct va_format vaf;
va_list args;
va_start(args, fmt);
vaf.fmt = fmt;
vaf.va = &args;
trace_batadv_dbg(bat_priv, &vaf);
va_end(args);
return 0;
}
Annotation
- Immediate include surface: `log.h`, `main.h`, `linux/stdarg.h`, `trace.h`.
- Detected declarations: `function batadv_debug_log`.
- Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
- 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.