Re: [PATCH bpf-next] bpf: Do not try bpf_msg_push_data with len 0

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 2/8/22 2:45 AM, Felix Maurer wrote:
If bpf_msg_push_data is called with len 0 (as it happens during
selftests/bpf/test_sockmap), we do not need to do anything and can
return early.

Signed-off-by: Felix Maurer <fmaurer@xxxxxxxxxx>
---
  net/core/filter.c | 3 +++
  1 file changed, 3 insertions(+)

diff --git a/net/core/filter.c b/net/core/filter.c
index 4603b7cd3cd1..9eb785842258 100644
--- a/net/core/filter.c
+++ b/net/core/filter.c
@@ -2710,6 +2710,9 @@ BPF_CALL_4(bpf_msg_push_data, struct sk_msg *, msg, u32, start,
  	if (unlikely(flags))
  		return -EINVAL;
+ if (unlikely(len == 0))
+		return 0;

If len == 0 is really unlikely in production environment, we
probably can keep it as is. There are some helpers like this
with a 'len' parameter, e.g., bpf_probe_read_kernel, bpf_probe_read_user, etc. which don't have 'size == 0' check.

John, could you also take a look?

+
  	/* First find the starting scatterlist element */
  	i = msg->sg.start;
  	do {



[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux