Home
last modified time | relevance | path

Searched refs:verifier (Results 1 – 25 of 45) sorted by relevance

12

/linux-6.1.9/Documentation/bpf/
Dverifier.rst3 eBPF verifier
18 If verifier sees an insn that does R2=R1, then R2 has now type
22 (In 'secure' mode verifier will reject any type of pointer arithmetic to make
60 A callback is used to customize verifier to restrict eBPF program access to only
68 If R6=PTR_TO_CTX, via is_valid_access() callback the verifier will know
70 the verifier will reject the program.
75 The verifier will allow eBPF program to read data from stack only after
78 Classic BPF verifier does similar check with M[0-15] memory slots.
92 The eBPF verifier will check that registers match argument constraints.
100 from safety point of view. The verifier will guarantee that the function is
[all …]
Dbpf_design_QA.rst90 Q: What are the verifier limits?
94 program can have. The verifier has various internal limits.
100 calls, a limit to the number of the verifier states per instruction,
104 to be rejected. The verifier used to recognize only pointer + constant
108 The verifier is steadily getting 'smarter'. The limits are
110 be accepted by the verifier is to try to load it.
183 compiling a program. Furthermore, the verifier can now mark the
191 enable zext insertion in the verifier).
194 support for zext. In that case, if verifier zext insertion is enabled,
226 space, but the verifier computes the actual amount of stack used
[all …]
Dkfuncs.rst55 by the verifier to make the usage of kernel functions safer and more useful.
70 Here, the verifier will treat first argument as a PTR_TO_MEM, and second
88 In addition to kfuncs' arguments, verifier may need more information about the
104 refcounted object. The verifier will then ensure that the pointer to the object
106 referenced kptr (by invoking bpf_kptr_xchg). If not, the verifier fails the
Dindex.rst16 verifier
Dringbuf.rst49 infrastructure that has to be built for observability and verifier support. It
98 submit records of the length that's not known to verifier beforehand. It also
107 be reserved, such that verifier can verify that BPF program can't access memory
118 Each reserved record is tracked by verifier through existing
175 header. This significantly simplifies verifier, as well as improving API
Dprog_lsm.rst90 the BPF verifier to update the offsets for the access at runtime using the
91 Documentation/bpf/btf.rst information. Since the BPF verifier is aware of the
Dbpf_devel_QA.rst219 Q: I made a BPF verifier change, do I need to add test cases for
222 A: If the patch has changes to the behavior of the verifier, then yes,
231 affect prior use-cases. Thus, treat those test cases as: verifier
422 To run the verifier tests::
426 The verifier tests print out all the current checks being
476 existing ones are adapted to verifier changes e.g. due to verifier
544 generation back end or about LLVM generated code that the verifier
653 into these structures is verified by the BPF verifier and may result
Dprog_flow_dissector.rst14 in BPF to gain all the benefits of BPF verifier (namely, limits on the
/linux-6.1.9/fs/nfs/
Dnfstrace.h330 const __be32 *verifier,
336 TP_ARGS(file, verifier, cookie, page_index, dtsize),
343 __array(char, verifier, NFS4_VERIFIER_SIZE)
358 memcpy(__entry->verifier, verifier,
361 memset(__entry->verifier, 0,
373 __entry->version, show_nfs4_verifier(__entry->verifier),
383 const __be32 *verifier, \
388 TP_ARGS(file, verifier, cookie, page_index, dtsize))
1409 __array(char, verifier, NFS4_VERIFIER_SIZE)
1424 memcpy(__entry->verifier,
[all …]
Dnfs3xdr.c275 static __be32 *xdr_encode_cookieverf3(__be32 *p, const __be32 *verifier) in xdr_encode_cookieverf3() argument
277 memcpy(p, verifier, NFS3_COOKIEVERFSIZE); in xdr_encode_cookieverf3()
281 static int decode_cookieverf3(struct xdr_stream *xdr, __be32 *verifier) in decode_cookieverf3() argument
288 memcpy(verifier, p, NFS3_COOKIEVERFSIZE); in decode_cookieverf3()
297 static void encode_createverf3(struct xdr_stream *xdr, const __be32 *verifier) in encode_createverf3() argument
302 memcpy(p, verifier, NFS3_CREATEVERFSIZE); in encode_createverf3()
305 static int decode_writeverf3(struct xdr_stream *xdr, struct nfs_write_verifier *verifier) in decode_writeverf3() argument
312 memcpy(verifier->data, p, NFS3_WRITEVERFSIZE); in decode_writeverf3()
1029 encode_createverf3(xdr, args->verifier); in encode_createhow3()
1703 if (decode_writeverf3(xdr, &result->verf->verifier)) in decode_write3resok()
[all …]
Dnfs42proc.c242 memcpy(&res->write_res.verifier, &copy->verf, sizeof(copy->verf)); in handle_async_copy()
268 if (nfs_write_verifier_cmp(&res->write_res.verifier.verifier, in process_copy_commit()
269 &cres.verf->verifier)) { in process_copy_commit()
382 nfs_write_verifier_cmp(&res->write_res.verifier.verifier, in _nfs42_proc_copy()
383 &res->commit_res.verf->verifier)) { in _nfs42_proc_copy()
396 res->write_res.verifier.committed != NFS_FILE_SYNC) { in _nfs42_proc_copy()
Dcallback_proc.c691 memcpy(&cp_state->verf.verifier.data[0], in nfs4_copy_cb_args()
692 &args->wr_writeverf.verifier.data[0], in nfs4_copy_cb_args()
Dnfs42xdr.c900 res->verifier.committed = be32_to_cpup(p); in decode_write_response()
901 return decode_verifier(xdr, &res->verifier.verifier); in decode_write_response()
/linux-6.1.9/tools/testing/selftests/bpf/
Dveristat.cfg2 # BPF verifier's performance on
DREADME.rst66 // the instructions below will not be seen in the verifier log
71 The verifier will reject such code with above error.
74 verifier to understand such speculative pointer arithmetic.
135 The verifier output looks like
163 This cause later verifier failure. The bug has been `fixed`__ in
DMakefile559 verifier/tests.h: verifier/*.c
560 $(shell ( cd verifier/; \
565 ) > verifier/tests.h)
566 $(OUTPUT)/test_verifier: test_verifier.c verifier/tests.h $(BPFOBJ) | $(OUTPUT)
613 prog_tests/tests.h map_tests/tests.h verifier/tests.h \
/linux-6.1.9/include/linux/
Dnfs_xdr.h468 nfs4_verifier verifier; /* EXCLUSIVE */ member
637 struct nfs_write_verifier verifier; member
922 __be32 verifier[2]; member
1139 nfs4_verifier verifier; member
1149 nfs4_verifier verifier; member
1324 nfs4_verifier verifier; member
1471 struct nfs_writeverf verifier; member
/linux-6.1.9/kernel/bpf/
DMakefile9 obj-$(CONFIG_BPF_SYSCALL) += syscall.o verifier.o inode.o helpers.o tnum.o bpf_iter.o map_iter.o ta…
/linux-6.1.9/drivers/net/ethernet/netronome/nfp/
DMakefile71 bpf/verifier.o \
/linux-6.1.9/tools/bpf/bpftool/Documentation/
Dcommon_options.rst24 logs from libbpf as well as from the verifier, when attempting to
/linux-6.1.9/Documentation/filesystems/nfs/
Dclient-identifier.rst56 - boot verifier: A 64-bit incarnation verifier that enables a
98 client presents a different boot verifier, so it appears to the
/linux-6.1.9/fs/nfsd/
Dtrace.h699 __array(unsigned char, verifier, NFS4_VERIFIER_SIZE)
707 memcpy(__entry->verifier, nn->writeverf,
712 __print_hex_str(__entry->verifier, NFS4_VERIFIER_SIZE)
785 __array(unsigned char, verifier, NFS4_VERIFIER_SIZE)
794 memcpy(__entry->verifier, (void *)&clp->cl_verifier,
800 __print_hex_str(__entry->verifier, NFS4_VERIFIER_SIZE),
Dnfs3proc.c285 u32 *verifier = (u32 *)argp->verf; in nfsd3_create_file() local
292 v_mtime = verifier[0] & 0x7fffffff; in nfsd3_create_file()
293 v_atime = verifier[1] & 0x7fffffff; in nfsd3_create_file()
/linux-6.1.9/Documentation/filesystems/
Dxfs-self-describing-metadata.rst220 A typical buffer read verifier is structured as follows::
243 The verifier function will take a couple of different forms, depending on
271 If there are different magic numbers for the different formats, the verifier
297 the opposite order to the read verifiers. A typical write verifier::
/linux-6.1.9/samples/bpf/
DREADME.rst4 This directory contains a test stubs, verifier test-suite and examples

12