BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: None <ruowenq2@illinois.edu>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, jinghao7@illinois.edu, keescook@chromium.org
Subject: Re: [PATCH bpf-next v3 0/1] samples/bpf: syscall_tp_user: Refactor and fix array index out-of-bounds bug
Date: Thu, 28 Sep 2023 16:40:22 +0000	[thread overview]
Message-ID: <169591922279.30419.2592606842232540042.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230927045030.224548-1-ruowenq2@illinois.edu>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Tue, 26 Sep 2023 23:50:29 -0500 you wrote:
> From: Ruowen Qin <ruowenq2@illinois.edu>
> 
> Thanks to Alexei, patch 2/3 and 3/3 from v2 have been upstreamed. v3
> primarily addresses scenarios where the compiler lacks ubsan support.
> 
> There are currently 6 BPF programs in syscall_tp_kern but the array to
> hold the corresponding bpf_links in syscall_tp_user only has space for 4
> programs, given the array size is hardcoded. This causes the sample
> program to fail due to an out-of-bound access that corrupts other stack
> variables:
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/1] samples/bpf: Add -fsanitize=bounds to userspace programs
    https://git.kernel.org/bpf/bpf-next/c/9e09b75079e2

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



      parent reply	other threads:[~2023-09-28 16:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27  4:50 [PATCH bpf-next v3 0/1] samples/bpf: syscall_tp_user: Refactor and fix array index out-of-bounds bug ruowenq2
2023-09-27  4:50 ` [PATCH bpf-next v3 1/1] samples/bpf: Add -fsanitize=bounds to userspace programs ruowenq2
2023-09-27 11:03   ` Jiri Olsa
2023-09-27 23:19     ` ruowenq2
2023-09-28  8:15       ` Jiri Olsa
2023-09-28  9:19         ` Jinghao Jia
2023-09-28 14:03           ` Jiri Olsa
2023-09-28 16:40 ` 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=169591922279.30419.2592606842232540042.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=jinghao7@illinois.edu \
    --cc=keescook@chromium.org \
    --cc=ruowenq2@illinois.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox