[bpf-next,v3,19/27] bpf: selftests: Get rid of bpf_rlimit.h

Message ID	20220405130858.12165-20-laoar.shao@gmail.com (mailing list archive)
State	New
Headers	show Return-Path: <linux-kselftest-owner@kernel.org> From: Yafang Shao <laoar.shao@gmail.com> To: andrii@kernel.org, ast@kernel.org, daniel@iogearbox.net, kafai@fb.com, songliubraving@fb.com, yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org, shuah@kernel.org Cc: netdev@vger.kernel.org, bpf@vger.kernel.org, linux-kselftest@vger.kernel.org, Yafang Shao <laoar.shao@gmail.com> Subject: [PATCH bpf-next v3 19/27] bpf: selftests: Get rid of bpf_rlimit.h Date: Tue, 5 Apr 2022 13:08:50 +0000 Message-Id: <20220405130858.12165-20-laoar.shao@gmail.com> In-Reply-To: <20220405130858.12165-1-laoar.shao@gmail.com> References: <20220405130858.12165-1-laoar.shao@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk
Series	bpf: RLIMIT_MEMLOCK cleanups \| expand [bpf-next,v3,00/27] bpf: RLIMIT_MEMLOCK cleanups [bpf-next,v3,01/27] bpf: selftests: Use libbpf 1.0 API mode instead of RLIMIT_MEMLOCK in xdping [bpf-next,v3,02/27] bpf: selftests: Use libbpf 1.0 API mode instead of RLIMIT_MEMLOCK in xdpxceiver [bpf-next,v3,03/27] bpf: selftests: No need to include bpf_rlimit.h in test_tcpnotify_user [bpf-next,v3,04/27] bpf: selftests: No need to include bpf_rlimit.h in flow_dissector_load [bpf-next,v3,05/27] bpf: selftests: Set libbpf 1.0 API mode explicitly in get_cgroup_id_user [bpf-next,v3,06/27] bpf: selftests: Set libbpf 1.0 API mode explicitly in test_cgroup_storage [bpf-next,v3,07/27] bpf: selftests: Set libbpf 1.0 API mode explicitly in get_cgroup_id_user [bpf-next,v3,08/27] bpf: selftests: Set libbpf 1.0 API mode explicitly in test_lpm_map [bpf-next,v3,09/27] bpf: selftests: Set libbpf 1.0 API mode explicitly in test_lru_map [bpf-next,v3,10/27] bpf: selftests: Set libbpf 1.0 API mode explicitly in test_skb_cgroup_id_user [bpf-next,v3,11/27] bpf: selftests: Set libbpf 1.0 API mode explicitly in test_sock_addr [bpf-next,v3,12/27] bpf: selftests: Set libbpf 1.0 API mode explicitly in test_sock [bpf-next,v3,13/27] bpf: selftests: Set libbpf 1.0 API mode explicitly in test_sockmap [bpf-next,v3,14/27] bpf: selftests: Set libbpf 1.0 API mode explicitly in test_sysctl [bpf-next,v3,15/27] bpf: selftests: Set libbpf 1.0 API mode explicitly in test_tag [bpf-next,v3,16/27] bpf: selftests: Set libbpf 1.0 API mode explicitly in test_tcp_check_syncookie_… [bpf-next,v3,17/27] bpf: selftests: Set libbpf 1.0 API mode explicitly in test_verifier_log [bpf-next,v3,18/27] bpf: samples: Set libbpf 1.0 API mode explicitly in hbm [bpf-next,v3,19/27] bpf: selftests: Get rid of bpf_rlimit.h [bpf-next,v3,20/27] bpf: selftests: No need to include sys/resource.h in some files [bpf-next,v3,21/27] bpf: samples: Use libbpf 1.0 API mode instead of RLIMIT_MEMLOCK in xdpsock_user [bpf-next,v3,22/27] bpf: samples: Use libbpf 1.0 API mode instead of RLIMIT_MEMLOCK in xsk_fwd [bpf-next,v3,23/27] bpf: samples: No need to include sys/resource.h in many files [bpf-next,v3,24/27] bpf: bpftool: Remove useless return value of libbpf_set_strict_mode [bpf-next,v3,25/27] bpf: bpftool: Set LIBBPF_STRICT_AUTO_RLIMIT_MEMLOCK for legacy libbpf [bpf-next,v3,26/27] bpf: bpftool: remove RLIMIT_MEMLOCK [bpf-next,v3,27/27] bpf: runqslower: Use libbpf 1.0 API mode instead of RLIMIT_MEMLOCK

Message ID

20220405130858.12165-20-laoar.shao@gmail.com (mailing list archive)

State

New

Headers

From: Yafang Shao <laoar.shao@gmail.com>
To: andrii@kernel.org, ast@kernel.org, daniel@iogearbox.net,
        kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
        john.fastabend@gmail.com, kpsingh@kernel.org, shuah@kernel.org
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
        linux-kselftest@vger.kernel.org, Yafang Shao <laoar.shao@gmail.com>
Subject: [PATCH bpf-next v3 19/27] bpf: selftests: Get rid of bpf_rlimit.h
Date: Tue,  5 Apr 2022 13:08:50 +0000
Message-Id: <20220405130858.12165-20-laoar.shao@gmail.com>
In-Reply-To: <20220405130858.12165-1-laoar.shao@gmail.com>
References: <20220405130858.12165-1-laoar.shao@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Series

bpf: RLIMIT_MEMLOCK cleanups | expand

Commit Message

Yafang Shao April 5, 2022, 1:08 p.m. UTC

All the files which included bpf_rlimit.h have been set strict mode
explicitly, so we can get rid of it now.

Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
---
 tools/testing/selftests/bpf/bpf_rlimit.h | 28 ------------------------
 1 file changed, 28 deletions(-)
 delete mode 100644 tools/testing/selftests/bpf/bpf_rlimit.h

diff --git a/tools/testing/selftests/bpf/bpf_rlimit.h b/tools/testing/selftests/bpf/bpf_rlimit.h
deleted file mode 100644
index 9dac9b30f8ef..000000000000
--- a/tools/testing/selftests/bpf/bpf_rlimit.h
+++ /dev/null
@@ -1,28 +0,0 @@ 
-#include <sys/resource.h>
-#include <stdio.h>
-
-static  __attribute__((constructor)) void bpf_rlimit_ctor(void)
-{
-	struct rlimit rlim_old, rlim_new = {
-		.rlim_cur	= RLIM_INFINITY,
-		.rlim_max	= RLIM_INFINITY,
-	};
-
-	getrlimit(RLIMIT_MEMLOCK, &rlim_old);
-	/* For the sake of running the test cases, we temporarily
-	 * set rlimit to infinity in order for kernel to focus on
-	 * errors from actual test cases and not getting noise
-	 * from hitting memlock limits. The limit is on per-process
-	 * basis and not a global one, hence destructor not really
-	 * needed here.
-	 */
-	if (setrlimit(RLIMIT_MEMLOCK, &rlim_new) < 0) {
-		perror("Unable to lift memlock rlimit");
-		/* Trying out lower limit, but expect potential test
-		 * case failures from this!
-		 */
-		rlim_new.rlim_cur = rlim_old.rlim_cur + (1UL << 20);
-		rlim_new.rlim_max = rlim_old.rlim_max + (1UL << 20);
-		setrlimit(RLIMIT_MEMLOCK, &rlim_new);
-	}
-}

[bpf-next,v3,19/27] bpf: selftests: Get rid of bpf_rlimit.h

Commit Message

Patch