Home
last modified time | relevance | path

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

12

/linux/Documentation/bpf/
A 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,
220 space, but the verifier computes the actual amount of stack used
[all …]
A 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
A Dbpf_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
A 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
A Dprog_flow_dissector.rst14 in BPF to gain all the benefits of BPF verifier (namely, limits on the
/linux/tools/testing/selftests/bpf/
A DREADME.rst58 // the instructions below will not be seen in the verifier log
63 The verifier will reject such code with above error.
66 verifier to understand such speculative pointer arithmetic.
127 The verifier output looks like
155 This cause later verifier failure. The bug has been `fixed`__ in
A DMakefile508 verifier/tests.h: verifier/*.c
509 $(shell ( cd verifier/; \
514 ) > verifier/tests.h)
515 $(OUTPUT)/test_verifier: test_verifier.c verifier/tests.h $(BPFOBJ) | $(OUTPUT)
545 prog_tests/tests.h map_tests/tests.h verifier/tests.h \
/linux/Documentation/networking/
A Dfilter.rst849 An in-kernel eBPF verifier is used to validate internal BPF programs.
1109 eBPF verifier
1123 If verifier sees an insn that does R2=R1, then R2 has now type
1175 the verifier will reject the program.
1183 Classic BPF verifier does similar check with M[0-15] memory slots.
1209 Seccomp solves this by two stage verifier: classic BPF verifier is followed
1210 by seccomp verifier. In case of eBPF one configurable verifier is shared for
1213 See details of eBPF verifier in kernel/bpf/verifier.c
1261 The verifier's knowledge about the variable offset consists of:
1328 has at least 14 directly accessible bytes. The verifier marks it
[all …]
/linux/fs/nfs/
A 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()
1702 if (decode_writeverf3(xdr, &result->verf->verifier)) in decode_write3resok()
[all …]
A Dnfs42proc.c239 memcpy(&res->write_res.verifier, &copy->verf, sizeof(copy->verf)); in handle_async_copy()
265 if (nfs_write_verifier_cmp(&res->write_res.verifier.verifier, in process_copy_commit()
266 &cres.verf->verifier)) { in process_copy_commit()
379 nfs_write_verifier_cmp(&res->write_res.verifier.verifier, in _nfs42_proc_copy()
380 &res->commit_res.verf->verifier)) { in _nfs42_proc_copy()
393 res->write_res.verifier.committed != NFS_FILE_SYNC) { in _nfs42_proc_copy()
A Dnfstrace.h1201 __array(char, verifier, NFS4_VERIFIER_SIZE)
1216 memcpy(__entry->verifier,
1217 &verf->verifier,
1234 show_nfs4_verifier(__entry->verifier)
1336 __array(char, verifier, NFS4_VERIFIER_SIZE)
1349 memcpy(__entry->verifier,
1350 &verf->verifier,
1365 show_nfs4_verifier(__entry->verifier)
A Dcallback_proc.c699 memcpy(&cp_state->verf.verifier.data[0], in nfs4_copy_cb_args()
700 &args->wr_writeverf.verifier.data[0], in nfs4_copy_cb_args()
A Dnfs42xdr.c892 res->verifier.committed = be32_to_cpup(p); in decode_write_response()
893 return decode_verifier(xdr, &res->verifier.verifier); in decode_write_response()
A Dnfs4xdr.c1446 encode_nfs4_verifier(xdr, &arg->u.verifier); in encode_createmode()
1450 encode_nfs4_verifier(xdr, &arg->u.verifier); in encode_createmode()
1634 encode_nfs4_verifier(xdr, &readdir->verifier); in encode_readdir()
1641 memcpy(verf, readdir->verifier.data, sizeof(verf)); in encode_readdir()
1799 encode_nfs4_verifier(xdr, &args->verifier); in encode_exchange_id()
4348 static int decode_verifier(struct xdr_stream *xdr, void *verifier) in decode_verifier() argument
4350 return decode_opaque_fixed(xdr, verifier, NFS4_VERIFIER_SIZE); in decode_verifier()
4365 status = decode_write_verifier(xdr, &verf->verifier); in decode_commit()
5265 status = decode_verifier(xdr, readdir->verifier.data); in decode_readdir()
5268 memcpy(verf, readdir->verifier.data, sizeof(verf)); in decode_readdir()
[all …]
A Dpnfs_nfs.c37 memset(&verf->verifier, 0, sizeof(verf->verifier)); in pnfs_generic_prepare_to_resend_writes()
A Dnfs3proc.c359 data->arg.create.verifier[0] = cpu_to_be32(jiffies); in nfs3_proc_create()
360 data->arg.create.verifier[1] = cpu_to_be32(current->pid); in nfs3_proc_create()
/linux/include/linux/
A Dnfs_xdr.h468 nfs4_verifier verifier; /* EXCLUSIVE */ member
637 struct nfs_write_verifier verifier; member
913 __be32 verifier[2]; member
1130 nfs4_verifier verifier; member
1140 nfs4_verifier verifier; member
1313 nfs4_verifier verifier; member
1460 struct nfs_writeverf verifier; member
/linux/tools/bpf/bpftool/Documentation/
A Dcommon_options.rst21 logs from libbpf as well as from the verifier, when attempting to
/linux/kernel/bpf/
A DMakefile9 obj-$(CONFIG_BPF_SYSCALL) += syscall.o verifier.o inode.o helpers.o tnum.o bpf_iter.o map_iter.o ta…
/linux/drivers/net/ethernet/netronome/nfp/
A DMakefile63 bpf/verifier.o \
/linux/fs/nfsd/
A Dvfs.h75 u32 *verifier, bool *truncp, bool *created);
A Dtrace.h609 __array(unsigned char, verifier, NFS4_VERIFIER_SIZE)
618 memcpy(__entry->verifier, (void *)&clp->cl_verifier,
624 __print_hex_str(__entry->verifier, NFS4_VERIFIER_SIZE),
A Dvfs.c1360 struct svc_fh *resfhp, int createmode, u32 *verifier, in do_nfsd_create() argument
1417 v_mtime = verifier[0]&0x7fffffff; in do_nfsd_create()
1418 v_atime = verifier[1]&0x7fffffff; in do_nfsd_create()
/linux/Documentation/filesystems/
A 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/samples/bpf/
A DREADME.rst4 This directory contains a test stubs, verifier test-suite and examples

Completed in 72 milliseconds

12