Re: [PATCH bpf-next v8 00/10] Registrating struct_ops types from modules

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 10/30/23 12:28 PM, thinker.li@xxxxxxxxx wrote:
Changes from v5:

  - As the 2nd patch, we introduce "bpf_struct_ops_desc". This change
    involves moving certain members of "bpf_struct_ops" to
    "bpf_struct_ops_desc", which becomes a part of
    "btf_struct_ops_tab". This ensures that these members remain
    accessible even when the owner module of a "bpf_struct_ops" is
    unloaded.

  - Correct the order of arguments when calling
     in the 3rd patch.

  - Remove the owner argument from bpf_struct_ops_init_one(). Instead,
    callers should fill in st_ops->owner.

  - Make sure to hold the owner module when calling
    bpf_struct_ops_find() and bpf_struct_ops_find_value() in the 6th
    patch.

  - Merge the functions register_bpf_struct_ops_btf() and
    register_bpf_struct_ops() into a single function and relocate it to
    btf.c for better organization and clarity.

  - Undo the name modifications made to find_kernel_btf_id() and

The find_kernel_attach_btf_id name change is still in patch 8. tbh, I don't have a strong preference on the name here. Could it be in a separate patch for naming cleanup or at least mention it in the commit message?






[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux