bpf: Plug a potential exclusive map memory leak #10297
Conversation
|
Upstream branch: 4722981 |
|
Upstream branch: 4722981 |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/1024000=>bpf-next
branch
from
73db13d to
c4d25c2
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
4a6b8b7 to
1efb39d
Compare
|
Upstream branch: 7dc211c |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/1024000=>bpf-next
branch
from
c4d25c2 to
5711b19
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
1efb39d to
5b97b4a
Compare
|
Upstream branch: ec12ab2 |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/1024000=>bpf-next
branch
from
5711b19 to
43c6308
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
5b97b4a to
7b6b51d
Compare
|
Upstream branch: d6ec090 |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/1024000=>bpf-next
branch
from
43c6308 to
9440b32
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
7b6b51d to
2412df8
Compare
|
Upstream branch: d6ec090 |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/1024000=>bpf-next
branch
from
9440b32 to
de63378
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
2412df8 to
bfb0726
Compare
|
Upstream branch: d088da9 |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/1024000=>bpf-next
branch
from
de63378 to
4baa49d
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
bfb0726 to
b0a5b86
Compare
|
Upstream branch: e0940c6 |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/1024000=>bpf-next
branch
from
4baa49d to
9f5a54f
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
b0a5b86 to
44cbecf
Compare
|
Upstream branch: 792f258 |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/1024000=>bpf-next
branch
from
9f5a54f to
a83562f
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
44cbecf to
e8ba78a
Compare
|
Upstream branch: 878ee3c |
When excl_prog_hash is 0 and excl_prog_hash_size is non-zero, the map also
needs to be freed. Otherwise, the map memory will not be reclaimed, just
like the memory leak problem reported by syzbot [1].
syzbot reported:
BUG: memory leak
backtrace (crc 7b9fb9b4):
map_create+0x322/0x11e0 kernel/bpf/syscall.c:1512
__sys_bpf+0x3556/0x3610 kernel/bpf/syscall.c:6131
Fixes: baefdbd ("bpf: Implement exclusive map creation")
Reported-by: [email protected]
Closes: https://syzkaller.appspot.com/bug?extid=cf08c551fecea9fd1320
Tested-by: [email protected]
Signed-off-by: Edward Adam Davis <[email protected]>
Acked-by: Yonghong Song <[email protected]>
kernel-patches-daemon-bpf
bot
force-pushed
the
series/1024000=>bpf-next
branch
from
a83562f to
e06b8bf
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
e8ba78a to
c1a1f03
Compare
|
At least one diff in series https://patchwork.kernel.org/project/netdevbpf/list/?series=1024000 irrelevant now. Closing PR. |
Pull request for series with
subject: bpf: Plug a potential exclusive map memory leak
version: 1
url: https://patchwork.kernel.org/project/netdevbpf/list/?series=1024000