On 2/17/23 5:50 AM, Alexander Lobakin wrote:
From: Kernel Test Robot <lkp@xxxxxxxxx>
Date: Fri, 17 Feb 2023 21:45:40 +0800
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: c068f40300a0eaa34f7105d137a5560b86951aa9
commit: 6c20822fada1b8adb77fa450d03a0d449686a4a9 [12987/13499] bpf, test_run: fix &xdp_frame misplacement for LIVE_FRAMES
config: ia64-randconfig-r025-20230213 (https://download.01.org/0day-ci/archive/20230217/202302172104.q3ddwzqu-lkp@xxxxxxxxx/config)
compiler: ia64-linux-gcc (GCC) 12.1.0
ia64 has 128-byte cacheline on some configs. While I can easily test it
in the kernel, what do I do in the userspace test >_<
Or just exclude non-{64,256} CLs from the assertion?
I would remove the static_assert from the kernel. Having a comment in the
xdp_do_redirect.c selftest is good enough. Considering the bpf supported archs
are more mainstream, it is easier for the xdp_do_redirect.c test to take care of it.
