diff options
| author | Alexei Starovoitov <ast@kernel.org> | 2022-12-04 12:52:40 -0800 |
|---|---|---|
| committer | Alexei Starovoitov <ast@kernel.org> | 2022-12-04 12:52:40 -0800 |
| commit | 1910676cc1ec29fad850448ead0fffdb93fb74b5 (patch) | |
| tree | ce785f382237fb42178ddb609ae78bfb334357bf /Documentation/bpf/index.rst | |
| parent | 706819495921ddad6b3780140b9d9e9293b6dedc (diff) | |
| parent | f53625649888c6ec9eeca151f802e905482c6698 (diff) | |
Merge branch 'bpf: Handle MEM_RCU type properly'
Yonghong Song says:
====================
Patch set [1] added rcu support for bpf programs. In [1], a rcu
pointer is considered to be trusted and not null. This is actually
not true in some cases. The rcu pointer could be null, and for non-null
rcu pointer, it may have reference count of 0. This small patch set
fixed this problem. Patch 1 is the kernel fix. Patch 2 adjusted
selftests properly. Patch 3 added documentation for newly-introduced
KF_RCU flag.
[1] https://lore.kernel.org/all/20221124053201.2372298-1-yhs@fb.com/
Changelogs:
v1 -> v2:
- rcu ptr could be NULL.
- non_null_rcu_ptr->rcu_field can be marked as MEM_RCU as well.
- Adjust the code to avoid existing error message change.
====================
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'Documentation/bpf/index.rst')
0 files changed, 0 insertions, 0 deletions