All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Edward Adam Davis <eadavis@qq.com>
Cc: syzbot+cf08c551fecea9fd1320@syzkaller.appspotmail.com,
	andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
	daniel@iogearbox.net, eddyz87@gmail.com, haoluo@google.com,
	john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org,
	linux-kernel@vger.kernel.org, martin.lau@linux.dev,
	sdf@fomichev.me, song@kernel.org,
	syzkaller-bugs@googlegroups.com, yonghong.song@linux.dev
Subject: Re: [PATCH] bpf: Plug a potential exclusive map memory leak
Date: Sat, 22 Nov 2025 00:52:58 +0000	[thread overview]
Message-ID: <176377277852.2637800.13726063744889483182.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_3F226F882CE56DCC94ACE90EED1ECCFC780A@qq.com>

Hello:

This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Sun, 16 Nov 2025 22:58:13 +0800 you wrote:
> 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
> 
> [...]

Here is the summary with links:
  - bpf: Plug a potential exclusive map memory leak
    https://git.kernel.org/bpf/bpf/c/22d70d400556

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-11-22  0:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-16 12:03 [syzbot] [bpf?] memory leak in map_create syzbot
2025-11-16 14:33 ` Edward Adam Davis
2025-11-16 14:57   ` syzbot
2025-11-16 14:58 ` [PATCH] bpf: Plug a potential exclusive map memory leak Edward Adam Davis
2025-11-17  6:06   ` Yonghong Song
2025-11-22  0:52   ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=176377277852.2637800.13726063744889483182.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eadavis@qq.com \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=sdf@fomichev.me \
    --cc=song@kernel.org \
    --cc=syzbot+cf08c551fecea9fd1320@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yonghong.song@linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.