tools/testing/selftests/bpf/progs/verifier_jeq_infer_not_null.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/bpf/progs/verifier_jeq_infer_not_null.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/bpf/progs/verifier_jeq_infer_not_null.c- Extension
.c- Size
- 8441 bytes
- Lines
- 268
- Domain
- Support Tooling And Documentation
- Bucket
- tools
- Inferred role
- Support Tooling And Documentation: implementation source
- Status
- source implementation candidate
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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/bpf.hbpf/bpf_helpers.hbpf_misc.h
Detected Declarations
function pointfunction __msgfunction __msg_unprivfunction __msgfunction __retvalfunction __log_levelfunction __log_level
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/* Converted from tools/testing/selftests/bpf/verifier/jeq_infer_not_null.c */
#include <linux/bpf.h>
#include <bpf/bpf_helpers.h>
#include "bpf_misc.h"
struct {
__uint(type, BPF_MAP_TYPE_XSKMAP);
__uint(max_entries, 1);
__type(key, int);
__type(value, int);
} map_xskmap SEC(".maps");
/* This is equivalent to the following program:
*
* r6 = skb->sk;
* r7 = sk_fullsock(r6);
* r0 = sk_fullsock(r6);
* if (r0 == 0) return 0; (a)
* if (r0 != r7) return 0; (b)
* *r7->type; (c)
* return 0;
*
* It is safe to dereference r7 at point (c), because of (a) and (b).
* The test verifies that relation r0 == r7 is propagated from (b) to (c).
*/
SEC("cgroup/skb")
__description("jne/jeq infer not null, PTR_TO_SOCKET_OR_NULL -> PTR_TO_SOCKET for JNE false branch")
__success __failure_unpriv __msg_unpriv("R7 pointer comparison")
__retval(0)
__naked void socket_for_jne_false_branch(void)
{
asm volatile (" \
/* r6 = skb->sk; */ \
r6 = *(u64*)(r1 + %[__sk_buff_sk]); \
/* if (r6 == 0) return 0; */ \
if r6 == 0 goto l0_%=; \
/* r7 = sk_fullsock(skb); */ \
r1 = r6; \
call %[bpf_sk_fullsock]; \
r7 = r0; \
/* r0 = sk_fullsock(skb); */ \
r1 = r6; \
call %[bpf_sk_fullsock]; \
/* if (r0 == null) return 0; */ \
if r0 == 0 goto l0_%=; \
/* if (r0 == r7) r0 = *(r7->type); */ \
if r0 != r7 goto l0_%=; /* Use ! JNE ! */\
r0 = *(u32*)(r7 + %[bpf_sock_type]); \
l0_%=: /* return 0 */ \
r0 = 0; \
exit; \
" :
: __imm(bpf_sk_fullsock),
__imm_const(__sk_buff_sk, offsetof(struct __sk_buff, sk)),
__imm_const(bpf_sock_type, offsetof(struct bpf_sock, type))
: __clobber_all);
}
/* Same as above, but verify that another branch of JNE still
* prohibits access to PTR_MAYBE_NULL.
*/
SEC("cgroup/skb")
__description("jne/jeq infer not null, PTR_TO_SOCKET_OR_NULL unchanged for JNE true branch")
__failure __msg("R7 invalid mem access 'sock_or_null'")
__failure_unpriv __msg_unpriv("R7 pointer comparison")
__naked void unchanged_for_jne_true_branch(void)
{
asm volatile (" \
/* r6 = skb->sk */ \
r6 = *(u64*)(r1 + %[__sk_buff_sk]); \
/* if (r6 == 0) return 0; */ \
if r6 == 0 goto l0_%=; \
/* r7 = sk_fullsock(skb); */ \
r1 = r6; \
call %[bpf_sk_fullsock]; \
r7 = r0; \
/* r0 = sk_fullsock(skb); */ \
r1 = r6; \
call %[bpf_sk_fullsock]; \
/* if (r0 == null) return 0; */ \
if r0 != 0 goto l0_%=; \
/* if (r0 == r7) return 0; */ \
if r0 != r7 goto l1_%=; /* Use ! JNE ! */\
goto l0_%=; \
l1_%=: /* r0 = *(r7->type); */ \
r0 = *(u32*)(r7 + %[bpf_sock_type]); \
l0_%=: /* return 0 */ \
r0 = 0; \
Annotation
- Immediate include surface: `linux/bpf.h`, `bpf/bpf_helpers.h`, `bpf_misc.h`.
- Detected declarations: `function point`, `function __msg`, `function __msg_unpriv`, `function __msg`, `function __retval`, `function __log_level`, `function __log_level`.
- Atlas domain: Support Tooling And Documentation / tools.
- 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.