JBPF program type and hook context naming convention

[amurgZainar]

Hello,

I have a question about the correspondence between the jbpf program type name (in case the default one, i.e., jbpf_generic is NOT the one being used) and the hook context name. Is there any association between the two? Is there any rule in naming the program type and the hook context that has to be followed? Following your examples, I see that the hook context name is the program type name followed by _ctx, but it's not clear whether this is just a coincidence or it's something mandatory.

For example, I have created the jbpf_ran_spectral_ctx and I have used the

SEC("jbpf_ran_spectral")
uint64_t
jbpf_main(void *state)

as the jbpf_ran_spectral program type in the codelet implementation.

Thanks!

[amurgZainar]

I think I’ve answered myself to one of the questions. There is no naming association between the program type and hook context by looking at jbpf_tests/verifier/jbpf_verifier_extension_test.cpp. When extending the verifier for the program type jbpf_my_prog_type, the name of the context is my_new_jbpf_ctx, which doesn't have anything in common in terms of naming with jbpf_my_prog_type. Although, I found it convenient to use this naming convention: <context_name> = <program_type_name>_ctx