From: Nick Desaulniers <ndesaulniers@google.com>
To: Justin Stitt <justinstitt@google.com>
Cc: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Shuah Khan <shuah@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
linux-input@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
Benjamin Tissoires <bentiss@kernel.org>,
llvm@lists.linux.dev
Subject: Re: [PATCH v2 0/3] selftests/hid: fix building for older kernels
Date: Fri, 8 Sep 2023 16:02:28 -0700 [thread overview]
Message-ID: <ZPuoBBGossSy0EiO@google.com> (raw)
In-Reply-To: <20230908-kselftest-09-08-v2-0-0def978a4c1b@google.com>
On Fri, Sep 08, 2023 at 10:22:37PM +0000, Justin Stitt wrote:
> Hi, I am sending this series on behalf of myself and Benjamin Tissoires. There
> existed an initial n=3 patch series which was later expanded to n=4 and
> is now back to n=3 with some fixes added in and rebased against
> mainline.
>
> This patch series aims to ensure that the hid/bpf selftests can be built
> without errors.
>
> Here's Benjamin's initial cover letter for context:
> | These fixes have been triggered by [0]:
> | basically, if you do not recompile the kernel first, and are
> | running on an old kernel, vmlinux.h doesn't have the required
> | symbols and the compilation fails.
> |
> | The tests will fail if you run them on that very same machine,
> | of course, but the binary should compile.
> |
> | And while I was sorting out why it was failing, I realized I
> | could do a couple of improvements on the Makefile.
> |
> | [0] https://lore.kernel.org/linux-input/56ba8125-2c6f-a9c9-d498-0ca1c153dcb2@redhat.com/T/#t
>
> Changes from v1 -> v2:
> - roll Justin's fix into patch 1/3
> - add __attribute__((preserve_access_index)) (thanks Eduard)
> - rebased onto mainline (2dde18cd1d8fac735875f2e4987f11817cc0bc2c)
> - Link to v1: https://lore.kernel.org/all/20230825-wip-selftests-v1-0-c862769020a8@kernel.org/
>
> Link: https://github.com/ClangBuiltLinux/linux/issues/1698
> Link: https://github.com/ClangBuiltLinux/continuous-integration2/issues/61
Thanks to you and Benjamin for sorting all of this out! With this series
applied, I was able to build the hid selftests now without the previous
-Wvisibility diagnostics failing the build.
Tested-by: Nick Desaulniers <ndesaulniers@google.com> # Build
> ---
> Benjamin Tissoires (3):
> selftests/hid: ensure we can compile the tests on kernels pre-6.3
> selftests/hid: do not manually call headers_install
> selftests/hid: force using our compiled libbpf headers
>
> tools/testing/selftests/hid/Makefile | 10 ++---
> tools/testing/selftests/hid/progs/hid.c | 3 --
> .../testing/selftests/hid/progs/hid_bpf_helpers.h | 49 ++++++++++++++++++++++
> 3 files changed, 53 insertions(+), 9 deletions(-)
> ---
> base-commit: 2dde18cd1d8fac735875f2e4987f11817cc0bc2c
> change-id: 20230908-kselftest-09-08-56d7f4a8d5c4
>
> Best regards,
> --
> Justin Stitt <justinstitt@google.com>
>
next prev parent reply other threads:[~2023-09-08 23:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 22:22 [PATCH v2 0/3] selftests/hid: fix building for older kernels Justin Stitt
2023-09-08 22:22 ` [PATCH v2 1/3] selftests/hid: ensure we can compile the tests on kernels pre-6.3 Justin Stitt
2023-09-11 13:19 ` Eduard Zingerman
2023-09-11 13:39 ` Benjamin Tissoires
2023-09-11 13:43 ` Eduard Zingerman
2023-09-08 22:22 ` [PATCH v2 2/3] selftests/hid: do not manually call headers_install Justin Stitt
2023-09-18 17:24 ` Shuah Khan
2023-09-08 22:22 ` [PATCH v2 3/3] selftests/hid: force using our compiled libbpf headers Justin Stitt
2023-09-08 23:02 ` Nick Desaulniers [this message]
2023-09-26 7:26 ` [PATCH v2 0/3] selftests/hid: fix building for older kernels Justin Stitt
2023-10-02 14:48 ` Benjamin Tissoires
2023-10-03 22:34 ` Justin Stitt
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=ZPuoBBGossSy0EiO@google.com \
--to=ndesaulniers@google.com \
--cc=benjamin.tissoires@redhat.com \
--cc=bentiss@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=jikos@kernel.org \
--cc=justinstitt@google.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=shuah@kernel.org \
/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