Home
last modified time | relevance | path

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

12

/Linux-v5.10/Documentation/bpf/
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,
214 space, but the verifier computes the actual amount of stack used
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
Dbpf_lsm.rst90 the BPF verifier to update the offsets for the access at runtime using the
91 :doc:`/bpf/btf` information. Since the BPF verifier is aware of the types, it
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
463 existing ones are adapted to verifier changes e.g. due to verifier
528 generation back end or about LLVM generated code that the verifier
637 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-v5.10/tools/testing/selftests/bpf/
DREADME.rst24 // the instructions below will not be seen in the verifier log
29 The verifier will reject such code with above error.
32 verifier to understand such speculative pointer arithmetic.
DMakefile425 verifier/tests.h: verifier/*.c
426 $(shell ( cd verifier/; \
431 ) > verifier/tests.h)
432 $(OUTPUT)/test_verifier: test_verifier.c verifier/tests.h $(BPFOBJ) | $(OUTPUT)
460 prog_tests/tests.h map_tests/tests.h verifier/tests.h \
/Linux-v5.10/Documentation/networking/
Dfilter.rst840 An in-kernel eBPF verifier is used to validate internal BPF programs.
871 Safety of internal BPF can come from a verifier (TBD). In such use cases as
1059 eBPF verifier
1073 If verifier sees an insn that does R2=R1, then R2 has now type
1077 (In 'secure' mode verifier will reject any type of pointer arithmetic to make
1115 A callback is used to customize verifier to restrict eBPF program access to only
1123 If R6=PTR_TO_CTX, via is_valid_access() callback the verifier will know
1125 the verifier will reject the program.
1130 The verifier will allow eBPF program to read data from stack only after
1133 Classic BPF verifier does similar check with M[0-15] memory slots.
[all …]
/Linux-v5.10/fs/nfs/
Dnfs3xdr.c272 static __be32 *xdr_encode_cookieverf3(__be32 *p, const __be32 *verifier) in xdr_encode_cookieverf3() argument
274 memcpy(p, verifier, NFS3_COOKIEVERFSIZE); in xdr_encode_cookieverf3()
278 static int decode_cookieverf3(struct xdr_stream *xdr, __be32 *verifier) in decode_cookieverf3() argument
285 memcpy(verifier, p, NFS3_COOKIEVERFSIZE); in decode_cookieverf3()
294 static void encode_createverf3(struct xdr_stream *xdr, const __be32 *verifier) in encode_createverf3() argument
299 memcpy(p, verifier, NFS3_CREATEVERFSIZE); in encode_createverf3()
302 static int decode_writeverf3(struct xdr_stream *xdr, struct nfs_write_verifier *verifier) in decode_writeverf3() argument
309 memcpy(verifier->data, p, NFS3_WRITEVERFSIZE); in decode_writeverf3()
1025 encode_createverf3(xdr, args->verifier); in encode_createhow3()
1698 if (decode_writeverf3(xdr, &result->verf->verifier)) in decode_write3resok()
[all …]
Dnfstrace.h1124 __array(char, verifier, NFS4_VERIFIER_SIZE)
1139 memcpy(__entry->verifier,
1140 &verf->verifier,
1157 __print_hex_str(__entry->verifier, NFS4_VERIFIER_SIZE)
1259 __array(char, verifier, NFS4_VERIFIER_SIZE)
1272 memcpy(__entry->verifier,
1273 &verf->verifier,
1288 __print_hex_str(__entry->verifier, NFS4_VERIFIER_SIZE)
Dnfs42proc.c227 memcpy(&res->write_res.verifier, &copy->verf, sizeof(copy->verf)); in handle_async_copy()
253 if (nfs_write_verifier_cmp(&res->write_res.verifier.verifier, in process_copy_commit()
254 &cres.verf->verifier)) { in process_copy_commit()
337 nfs_write_verifier_cmp(&res->write_res.verifier.verifier, in _nfs42_proc_copy()
338 &res->commit_res.verf->verifier)) { in _nfs42_proc_copy()
351 res->write_res.verifier.committed != NFS_FILE_SYNC) { in _nfs42_proc_copy()
Dcallback_proc.c693 memcpy(&cp_state->verf.verifier.data[0], in nfs4_copy_cb_args()
694 &args->wr_writeverf.verifier.data[0], in nfs4_copy_cb_args()
Dnfs42xdr.c886 res->verifier.committed = be32_to_cpup(p); in decode_write_response()
887 return decode_verifier(xdr, &res->verifier.verifier); in decode_write_response()
Dpnfs_nfs.c37 memset(&verf->verifier, 0, sizeof(verf->verifier)); in pnfs_generic_prepare_to_resend_writes()
Dnfs3proc.c337 data->arg.create.verifier[0] = cpu_to_be32(jiffies); in nfs3_proc_create()
338 data->arg.create.verifier[1] = cpu_to_be32(current->pid); in nfs3_proc_create()
Dnfs4xdr.c1434 encode_nfs4_verifier(xdr, &arg->u.verifier); in encode_createmode()
1438 encode_nfs4_verifier(xdr, &arg->u.verifier); in encode_createmode()
1622 encode_nfs4_verifier(xdr, &readdir->verifier); in encode_readdir()
1629 memcpy(verf, readdir->verifier.data, sizeof(verf)); in encode_readdir()
1787 encode_nfs4_verifier(xdr, &args->verifier); in encode_exchange_id()
4328 static int decode_verifier(struct xdr_stream *xdr, void *verifier) in decode_verifier() argument
4330 return decode_opaque_fixed(xdr, verifier, NFS4_VERIFIER_SIZE); in decode_verifier()
4333 static int decode_write_verifier(struct xdr_stream *xdr, struct nfs_write_verifier *verifier) in decode_write_verifier() argument
4335 return decode_opaque_fixed(xdr, verifier->data, NFS4_VERIFIER_SIZE); in decode_write_verifier()
4345 status = decode_write_verifier(xdr, &verf->verifier); in decode_commit()
[all …]
Dnfs4proc.c314 static void nfs4_setup_readdir(u64 cookie, __be32 *verifier, struct dentry *dentry, in nfs4_setup_readdir() argument
322 memcpy(&readdir->verifier, verifier, sizeof(readdir->verifier)); in nfs4_setup_readdir()
327 memset(&readdir->verifier, 0, sizeof(readdir->verifier)); in nfs4_setup_readdir()
1363 memcpy(p->o_arg.u.verifier.data, c->verf, in nfs4_opendata_alloc()
1364 sizeof(p->o_arg.u.verifier.data)); in nfs4_opendata_alloc()
4988 memcpy(NFS_I(dir)->cookieverf, res.verifier.data, NFS4_VERIFIER_SIZE); in _nfs4_proc_readdir()
8462 nfs4_init_boot_verifier(clp, &calldata->args.verifier); in nfs4_run_exchange_id()
8501 memcpy(calldata->args.verifier.data, clp->cl_confirm.data, in nfs4_run_exchange_id()
8502 sizeof(calldata->args.verifier.data)); in nfs4_run_exchange_id()
8585 memcpy(clp->cl_confirm.data, argp->verifier.data, in _nfs4_proc_exchange_id()
/Linux-v5.10/include/linux/
Dnfs_xdr.h463 nfs4_verifier verifier; /* EXCLUSIVE */ member
631 struct nfs_write_verifier verifier; member
894 __be32 verifier[2]; member
1116 nfs4_verifier verifier; member
1126 nfs4_verifier verifier; member
1299 nfs4_verifier verifier; member
1446 struct nfs_writeverf verifier; member
/Linux-v5.10/tools/bpf/bpftool/Documentation/
Dcommon_options.rst21 logs from libbpf as well as from the verifier, when attempting to
/Linux-v5.10/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-v5.10/drivers/net/ethernet/netronome/nfp/
DMakefile62 bpf/verifier.o \
/Linux-v5.10/fs/nfsd/
Dvfs.h75 u32 *verifier, bool *truncp, bool *created);
Dvfs.c1369 struct svc_fh *resfhp, int createmode, u32 *verifier, in do_nfsd_create() argument
1425 v_mtime = verifier[0]&0x7fffffff; in do_nfsd_create()
1426 v_atime = verifier[1]&0x7fffffff; in do_nfsd_create()
/Linux-v5.10/samples/bpf/
DREADME.rst4 This directory contains a test stubs, verifier test-suite and examples
/Linux-v5.10/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::

12