diff options
author | Alexei Starovoitov <ast@kernel.org> | 2023-12-13 20:49:11 -0800 |
---|---|---|
committer | Alexei Starovoitov <ast@kernel.org> | 2023-12-13 21:02:40 -0800 |
commit | c838fe1282df540ebf6e24e386ac34acb3ef3115 (patch) | |
tree | 0b6e496130744349f7e15d3c015e7196e9bb7217 /lib/net_utils.c | |
parent | 2a0c6b41eec90c2a138ea8b574836744783c67ff (diff) | |
parent | dc68540913ac523b46ebda3843cec179362c7a72 (diff) |
Merge branch 'bpf-use-gfp_kernel-in-bpf_event_entry_gen'
Hou Tao says:
====================
The simple patch set aims to replace GFP_ATOMIC by GFP_KERNEL in
bpf_event_entry_gen(). These two patches in the patch set were
preparatory patches in "Fix the release of inner map" patchset [1] and
are not needed for v2, so re-post it to bpf-next tree.
Patch #1 reduces the scope of rcu_read_lock when updating fd map and
patch #2 replaces GFP_ATOMIC by GFP_KERNEL. Please see individual
patches for more details.
Change Log:
v3:
* patch #1: fallback to patch #1 in v1. Update comments in
bpf_fd_htab_map_update_elem() to explain the reason for
rcu_read_lock() (Alexei)
v2: https://lore.kernel.org/bpf/20231211073843.1888058-1-houtao@huaweicloud.com/
* patch #1: add rcu_read_lock/unlock() for bpf_fd_array_map_update_elem
as well to make it consistent with
bpf_fd_htab_map_update_elem and update commit message
accordingly (Alexei)
* patch #1/#2: collects ack tags from Yonghong
v1: https://lore.kernel.org/bpf/20231208103357.2637299-1-houtao@huaweicloud.com/
[1]: https://lore.kernel.org/bpf/20231107140702.1891778-1-houtao@huaweicloud.com/
====================
Link: https://lore.kernel.org/r/20231214043010.3458072-1-houtao@huaweicloud.com
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'lib/net_utils.c')
0 files changed, 0 insertions, 0 deletions