Home
last modified time | relevance | path

Searched refs:REG_LIVE_WRITTEN (Results 1 – 4 of 4) sorted by relevance

/linux/kernel/bpf/
H A Dlog.c546 if (live & (REG_LIVE_READ | REG_LIVE_WRITTEN | REG_LIVE_DONE)) in print_liveness()
550 if (live & REG_LIVE_WRITTEN) in print_liveness()
H A Dverifier.c771 state->stack[spi].spilled_ptr.live |= REG_LIVE_WRITTEN; in mark_stack_slots_dynptr()
772 state->stack[spi - 1].spilled_ptr.live |= REG_LIVE_WRITTEN; in mark_stack_slots_dynptr()
810 state->stack[spi].spilled_ptr.live |= REG_LIVE_WRITTEN; in invalidate_dynptr()
811 state->stack[spi - 1].spilled_ptr.live |= REG_LIVE_WRITTEN; in invalidate_dynptr()
921 state->stack[spi].spilled_ptr.live |= REG_LIVE_WRITTEN; in destroy_if_dynptr_stack_slot()
922 state->stack[spi - 1].spilled_ptr.live |= REG_LIVE_WRITTEN; in destroy_if_dynptr_stack_slot()
1040 st->live |= REG_LIVE_WRITTEN; in mark_stack_slots_iter()
1076 st->live |= REG_LIVE_WRITTEN; in unmark_stack_slots_iter()
1171 st->live |= REG_LIVE_WRITTEN; in mark_stack_slot_irq_flag()
1215 st->live |= REG_LIVE_WRITTEN; in unmark_stack_slot_irq_flag()
[all …]
/linux/Documentation/bpf/
H A Dverifier.rst360 REG_LIVE_WRITTEN = 0x4,
392 * ``REG_LIVE_WRITTEN`` means that the value of the register (or stack slot) is
494 if state->live & REG_LIVE_WRITTEN:
516 Because stack writes could have different sizes ``REG_LIVE_WRITTEN`` marks are
528 As stated above, the write at (1) does not count as ``REG_LIVE_WRITTEN``. Should
/linux/include/linux/
H A Dbpf_verifier.h47 REG_LIVE_WRITTEN = 0x4, /* reg was written first, screening off later reads */ enumerator