From: Martin KaFai Lau <martin.lau@linux.dev>
To: Stanislav Fomichev <sdf@google.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
song@kernel.org, yhs@fb.com, john.fastabend@gmail.com,
kpsingh@kernel.org, haoluo@google.com, jolsa@kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v6 2/4] selftests/bpf: Update EFAULT {g,s}etsockopt selftests
Date: Sat, 13 May 2023 17:08:14 -0700 [thread overview]
Message-ID: <a5a9c29b-dd95-bbdf-2fd3-303527edac51@linux.dev> (raw)
In-Reply-To: <20230511170456.1759459-3-sdf@google.com>
On 5/11/23 10:04 AM, Stanislav Fomichev wrote:
> @@ -946,6 +1030,9 @@ static int run_test(int cgroup_fd, struct sockopt_test *test)
> goto free_optval;
> }
>
> + if (optlen > sizeof(test->get_optval))
> + optlen = sizeof(test->get_optval);
> +
Applied with this if statement removed. It is no longer needed. Let me know if
the removal was a mistake. Thanks.
next prev parent reply other threads:[~2023-05-14 0:08 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 [this message]
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 ` [PATCH bpf-next v6 0/4] bpf: Don't EFAULT for {g,s}setsockopt with wrong optlen patchwork-bot+netdevbpf
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=a5a9c29b-dd95-bbdf-2fd3-303527edac51@linux.dev \
--to=martin.lau@linux.dev \
--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=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 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.