mirror of
https://github.com/JakeHillion/drgn.git
synced 2024-12-22 17:23:06 +00:00
200d870b98
Like `list_bpf_progs()` and `list_bpf_maps()`, it's easy to implement
`list_bpf_links()`.
Here's an use example:
```bash
drgn ./contrib/bpf_inspect.py l
1: BPF_LINK_TYPE_TRACING prog: 2: BPF_PROG_TYPE_TRACING hid_tail_call
931: BPF_LINK_TYPE_XDP prog: 2056: BPF_PROG_TYPE_XDP dummy
932: BPF_LINK_TYPE_TRACING prog: 2060: BPF_PROG_TYPE_TRACING fentry_xdp
933: BPF_LINK_TYPE_TRACING prog: 2061: BPF_PROG_TYPE_TRACING fexit_xdp
```
Signed-off-by: Leon Hwang <hffilwlqm@gmail.com>
|
||
|---|---|---|
| .. | ||
| bpf_inspect.py | ||
| btrfs_orphan_subvolumes.py | ||
| btrfs_tree_mod_log.py | ||
| btrfs_tree.py | ||
| cgroup.py | ||
| dm_crypt_key.py | ||
| dump_btrfs_bgs.py | ||
| find_struct_file.py | ||
| fs_inodes.py | ||
| gcore.py | ||
| irq.py | ||
| kcore_list.py | ||
| kernel_sys.py | ||
| lsmod.py | ||
| mount.py | ||
| negdentdelete.py | ||
| platform_drivers.py | ||
| ps.py | ||
| ptdrgn.py | ||
| README.rst | ||
| search_kernel_memory.py | ||
| stack_trace_call_fault.py | ||
| tcp_sock.py | ||
| vmmap.py | ||
| vmstat.py | ||
Community-Contributed Content ============================= This directory contains drgn scripts, libraries, and notes that have been contributed by the community but aren't considered a part of drgn proper. Code in this directory is not tested and not necessarily up to the rest of the project's standards. This is intended as a central location to share drgn ideas with a low barrier to entry. If you have time to polish your code, consider submitting it as a proper helper or tool. If not, feel free to dump it here. Someone else might find it useful as a starting point for their own investigation. It could even be adapted into a helper or tool later. Contributing to ``contrib`` --------------------------- The bar for contributing to ``contrib`` is intentionally low. Code submitted here can be rough and will be only lightly reviewed. The only hard requirements are: * It must be relevant to drgn. * All files must have a comment or docstring at the top describing what they are. This can be short. There are also some boring legal requirements: * All files must have a copyright notice. * All files must be licensed under the LGPLv2.1+ (using ``SPDX-License-Identifier: LGPL-2.1-or-later``). * All commits must have a ``Signed-off-by`` trailer. See `Signing Off <../CONTRIBUTING.rst#signing-off>`_. We may choose to edit, reorganize, or drop parts your contribution. If in doubt, go ahead and open a pull request, and we'll decide what to do with it.