From: Martin KaFai Lau <martin.lau@linux.dev>
To: "Alexander Lobakin" <aleksander.lobakin@intel.com>,
"Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev, kernel test robot <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
bpf@vger.kernel.org, Martin KaFai Lau <martin.lau@kernel.org>
Subject: Re: [linux-next:master 12987/13499] include/linux/build_bug.h:78:41: error: static assertion failed: "SKB_WITH_OVERHEAD(TEST_XDP_FRAME_SIZE - XDP_PACKET_HEADROOM) == TEST_MAX_PKT_SIZE"
Date: Fri, 17 Feb 2023 10:33:30 -0800 [thread overview]
Message-ID: <58374b80-34b6-4c4f-b7bd-9c2f6be3eba6@linux.dev> (raw)
In-Reply-To: <50c35055-afa9-d01e-9a05-ea5351280e4f@intel.com>
On 2/17/23 5:50 AM, Alexander Lobakin wrote:
> From: Kernel Test Robot <lkp@intel.com>
> 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@intel.com/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.
prev parent reply other threads:[~2023-02-17 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 13:45 [linux-next:master 12987/13499] include/linux/build_bug.h:78:41: error: static assertion failed: "SKB_WITH_OVERHEAD(TEST_XDP_FRAME_SIZE - XDP_PACKET_HEADROOM) == TEST_MAX_PKT_SIZE" kernel test robot
2023-02-17 13:50 ` Alexander Lobakin
2023-02-17 18:33 ` Martin KaFai Lau [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=58374b80-34b6-4c4f-b7bd-9c2f6be3eba6@linux.dev \
--to=martin.lau@linux.dev \
--cc=aleksander.lobakin@intel.com \
--cc=bpf@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=martin.lau@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=toke@redhat.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;
as well as URLs for NNTP newsgroup(s).