From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <sdf@google.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
haoluo@google.com, jolsa@kernel.org
Subject: Re: [PATCH bpf-next v6 0/4] bpf: Don't EFAULT for {g,s}setsockopt with wrong optlen
Date: Sun, 14 May 2023 00:10:21 +0000 [thread overview]
Message-ID: <168402302119.7162.15862761284178303387.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230511170456.1759459-1-sdf@google.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Thu, 11 May 2023 10:04:52 -0700 you wrote:
> optval larger than PAGE_SIZE leads to EFAULT if the BPF program
> isn't careful enough. This is often overlooked and might break
> completely unrelated socket options. Instead of EFAULT,
> let's ignore BPF program buffer changes. See the first patch for
> more info.
>
> In addition, clearly document this corner case and reset optlen
> in our selftests (in case somebody copy-pastes from them).
>
> [...]
Here is the summary with links:
- [bpf-next,v6,1/4] bpf: Don't EFAULT for {g,s}setsockopt with wrong optlen
https://git.kernel.org/bpf/bpf-next/c/29ebbba7d461
- [bpf-next,v6,2/4] selftests/bpf: Update EFAULT {g,s}etsockopt selftests
https://git.kernel.org/bpf/bpf-next/c/989a4a7dbff2
- [bpf-next,v6,3/4] selftests/bpf: Correctly handle optlen > 4096
https://git.kernel.org/bpf/bpf-next/c/e01b4a72f132
- [bpf-next,v6,4/4] bpf: Document EFAULT changes for sockopt
https://git.kernel.org/bpf/bpf-next/c/6b6a23d5d8e8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-05-14 0:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 17:04 [PATCH bpf-next v6 0/4] bpf: Don't EFAULT for {g,s}setsockopt with wrong optlen Stanislav Fomichev
2023-05-11 17:04 ` [PATCH bpf-next v6 1/4] " Stanislav Fomichev
2023-05-11 17:04 ` [PATCH bpf-next v6 2/4] selftests/bpf: Update EFAULT {g,s}etsockopt selftests Stanislav Fomichev
2023-05-14 0:08 ` Martin KaFai Lau
2023-05-11 17:04 ` [PATCH bpf-next v6 3/4] selftests/bpf: Correctly handle optlen > 4096 Stanislav Fomichev
2023-05-11 17:04 ` [PATCH bpf-next v6 4/4] bpf: Document EFAULT changes for sockopt Stanislav Fomichev
2023-05-14 0:10 ` 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=168402302119.7162.15862761284178303387.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.com \
/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