Home
last modified time | relevance | path

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

12

/Linux-v5.4/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
Dbpf_devel_QA.rst224 Q: I made a BPF verifier change, do I need to add test cases for
227 A: If the patch has changes to the behavior of the verifier, then yes,
236 affect prior use-cases. Thus, treat those test cases as: verifier
427 To run the verifier tests::
431 The verifier tests print out all the current checks being
453 existing ones are adapted to verifier changes e.g. due to verifier
513 generation back end or about LLVM generated code that the verifier
622 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.4/fs/nfs/
Dnfstrace.h960 __field(unsigned long long, verifier)
972 memcpy(&__entry->verifier, &writeverf->verifier,
973 sizeof(__entry->verifier));
988 __entry->verifier
1038 __field(unsigned long long, verifier)
1050 memcpy(&__entry->verifier, &data->verf.verifier,
1051 sizeof(__entry->verifier));
1064 __entry->verifier
Dnfs42proc.c185 memcpy(&res->write_res.verifier, &copy->verf, sizeof(copy->verf)); in handle_async_copy()
209 if (nfs_write_verifier_cmp(&res->write_res.verifier.verifier, in process_copy_commit()
210 &cres.verf->verifier)) { in process_copy_commit()
276 nfs_write_verifier_cmp(&res->write_res.verifier.verifier, in _nfs42_proc_copy()
277 &res->commit_res.verf->verifier)) { in _nfs42_proc_copy()
290 res->write_res.verifier.committed != NFS_FILE_SYNC) { in _nfs42_proc_copy()
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()
1029 encode_createverf3(xdr, args->verifier); in encode_createhow3()
1702 if (decode_writeverf3(xdr, &result->verf->verifier)) in decode_write3resok()
[all …]
Dnfs42xdr.c489 res->verifier.committed = be32_to_cpup(p); in decode_write_response()
490 return decode_verifier(xdr, &res->verifier.verifier); in decode_write_response()
Dpnfs_nfs.c37 memcpy(&data->verf.verifier, &first->wb_verf, in pnfs_generic_prepare_to_resend_writes()
38 sizeof(data->verf.verifier)); in pnfs_generic_prepare_to_resend_writes()
39 data->verf.verifier.data[0]++; /* ensure verifier mismatch */ in pnfs_generic_prepare_to_resend_writes()
Dcallback_proc.c690 memcpy(&cp_state->verf.verifier.data[0], in nfs4_copy_cb_args()
691 &args->wr_writeverf.verifier.data[0], in nfs4_copy_cb_args()
Ddirect.c206 return nfs_write_verifier_cmp(&v1->verifier, &v2->verifier); in nfs_direct_cmp_verf()
Dnfs3proc.c327 data->arg.create.verifier[0] = cpu_to_be32(jiffies); in nfs3_proc_create()
328 data->arg.create.verifier[1] = cpu_to_be32(current->pid); in nfs3_proc_create()
Dnfs4xdr.c1437 encode_nfs4_verifier(xdr, &arg->u.verifier); in encode_createmode()
1441 encode_nfs4_verifier(xdr, &arg->u.verifier); in encode_createmode()
1625 encode_nfs4_verifier(xdr, &readdir->verifier); in encode_readdir()
1632 memcpy(verf, readdir->verifier.data, sizeof(verf)); in encode_readdir()
1790 encode_nfs4_verifier(xdr, &args->verifier); in encode_exchange_id()
4307 static int decode_verifier(struct xdr_stream *xdr, void *verifier) in decode_verifier() argument
4309 return decode_opaque_fixed(xdr, verifier, NFS4_VERIFIER_SIZE); in decode_verifier()
4312 static int decode_write_verifier(struct xdr_stream *xdr, struct nfs_write_verifier *verifier) in decode_write_verifier() argument
4314 return decode_opaque_fixed(xdr, verifier->data, NFS4_VERIFIER_SIZE); in decode_write_verifier()
4323 status = decode_write_verifier(xdr, &res->verf->verifier); in decode_commit()
[all …]
Dnfs4proc.c305 static void nfs4_setup_readdir(u64 cookie, __be32 *verifier, struct dentry *dentry, in nfs4_setup_readdir() argument
313 memcpy(&readdir->verifier, verifier, sizeof(readdir->verifier)); in nfs4_setup_readdir()
318 memset(&readdir->verifier, 0, sizeof(readdir->verifier)); in nfs4_setup_readdir()
1303 memcpy(p->o_arg.u.verifier.data, c->verf, in nfs4_opendata_alloc()
1304 sizeof(p->o_arg.u.verifier.data)); in nfs4_opendata_alloc()
4867 memcpy(NFS_I(dir)->cookieverf, res.verifier.data, NFS4_VERIFIER_SIZE); in _nfs4_proc_readdir()
8104 nfs4_init_boot_verifier(clp, &calldata->args.verifier); in nfs4_run_exchange_id()
8143 memcpy(calldata->args.verifier.data, clp->cl_confirm.data, in nfs4_run_exchange_id()
8144 sizeof(calldata->args.verifier.data)); in nfs4_run_exchange_id()
8223 memcpy(clp->cl_confirm.data, argp->verifier.data, in _nfs4_proc_exchange_id()
/Linux-v5.4/Documentation/networking/
Dfilter.txt806 An in-kernel eBPF verifier is used to validate internal BPF programs.
837 Safety of internal BPF can come from a verifier (TBD). In such use cases as
1019 eBPF verifier
1033 If verifier sees an insn that does R2=R1, then R2 has now type
1037 (In 'secure' mode verifier will reject any type of pointer arithmetic to make
1067 A callback is used to customize verifier to restrict eBPF program access to only
1073 If R6=PTR_TO_CTX, via is_valid_access() callback the verifier will know
1075 the verifier will reject the program.
1080 The verifier will allow eBPF program to read data from stack only after
1082 Classic BPF verifier does similar check with M[0-15] memory slots.
[all …]
/Linux-v5.4/kernel/bpf/
DMakefile5 obj-$(CONFIG_BPF_SYSCALL) += syscall.o verifier.o inode.o helpers.o tnum.o
/Linux-v5.4/tools/testing/selftests/bpf/
DMakefile303 VERIFIER_TESTS_DIR = $(OUTPUT)/verifier
307 VERIFIER_TEST_FILES := $(wildcard verifier/*.c)
312 $(shell ( cd verifier/; \
/Linux-v5.4/include/linux/
Dnfs_xdr.h461 nfs4_verifier verifier; /* EXCLUSIVE */ member
629 struct nfs_write_verifier verifier; member
892 __be32 verifier[2]; member
1114 nfs4_verifier verifier; member
1124 nfs4_verifier verifier; member
1288 nfs4_verifier verifier; member
1443 struct nfs_writeverf verifier; member
/Linux-v5.4/drivers/net/ethernet/netronome/nfp/
DMakefile62 bpf/verifier.o \
/Linux-v5.4/tools/bpf/bpftool/Documentation/
Dbpftool.rst71 includes logs from libbpf as well as from the verifier, when
/Linux-v5.4/fs/nfsd/
Dvfs.h72 u32 *verifier, bool *truncp, bool *created);
Dvfs.c1296 struct svc_fh *resfhp, int createmode, u32 *verifier, in do_nfsd_create() argument
1352 v_mtime = verifier[0]&0x7fffffff; in do_nfsd_create()
1353 v_atime = verifier[1]&0x7fffffff; in do_nfsd_create()
Dxdr4.h404 nfs4_verifier verifier; member
Dnfs4proc.c569 static void gen_boot_verifier(nfs4_verifier *verifier, struct net *net) in gen_boot_verifier() argument
571 __be32 *verf = (__be32 *)verifier->data; in gen_boot_verifier()
573 BUILD_BUG_ON(2*sizeof(*verf) != sizeof(verifier->data)); in gen_boot_verifier()
/Linux-v5.4/samples/bpf/
DREADME.rst4 This directory contains a test stubs, verifier test-suite and examples
/Linux-v5.4/Documentation/filesystems/
Dxfs-self-describing-metadata.txt217 A typical buffer read verifier is structured as follows:
240 The verifier function will take a couple of different forms, depending on
268 If there are different magic numbers for the different formats, the verifier
294 the opposite order to the read verifiers. A typical write verifier:

12