From: "kernelci.org bot" <bot@kernelci.org>
To: kernelci-results@groups.io, linux-kselftest@vger.kernel.org,
shuah@kernel.org
Subject: kselftest/fixes build: 6 builds: 0 failed, 6 passed, 6 warnings (linux-kselftest-fixes-6.4-rc3)
Date: Wed, 17 May 2023 12:24:52 -0700 (PDT) [thread overview]
Message-ID: <64652a04.170a0220.4c0ca.32fa@mx.google.com> (raw)
kselftest/fixes build: 6 builds: 0 failed, 6 passed, 6 warnings (linux-kselftest-fixes-6.4-rc3)
Full Build Summary: https://kernelci.org/build/kselftest/branch/fixes/kernel/linux-kselftest-fixes-6.4-rc3/
Tree: kselftest
Branch: fixes
Git Describe: linux-kselftest-fixes-6.4-rc3
Git Commit: dbcf76390eb9a65d5d0c37b0cd57335218564e37
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git
Built: 4 unique architectures
Warnings Detected:
arm64:
arm:
i386:
x86_64:
x86_64_defconfig+kselftest (gcc-10): 3 warnings
x86_64_defconfig+kselftest (clang-16): 3 warnings
Warnings summary:
1 vmlinux.o: warning: objtool: set_ftrace_ops_ro+0x3e: relocation to !ENDBR: .text+0x1423b6
1 vmlinux.o: warning: objtool: set_ftrace_ops_ro+0x28: relocation to !ENDBR: .text+0x14252b
1 vmlinux.o: warning: objtool: lkdtm_UNSET_SMEP+0xca: relocation to !ENDBR: native_write_cr4+0x4
1 vmlinux.o: warning: objtool: iovec_from_user+0x88: call to copy_iovec_from_user.part.0() with UACCESS enabled
1 vmlinux.o: warning: objtool: __import_iovec+0x147: call to copy_iovec_from_user.part.0() with UACCESS enabled
1 vmlinux.o: warning: objtool: .altinstr_replacement+0x1d1b: redundant UACCESS disable
================================================================================
Detailed per-defconfig build reports:
--------------------------------------------------------------------------------
defconfig+kselftest (arm64, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
defconfig+kselftest+arm64-chromebook (arm64, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
i386_defconfig+kselftest (i386, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
multi_v7_defconfig+kselftest (arm, gcc-10) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
x86_64_defconfig+kselftest (x86_64, gcc-10) — PASS, 0 errors, 3 warnings, 0 section mismatches
Warnings:
vmlinux.o: warning: objtool: .altinstr_replacement+0x1d1b: redundant UACCESS disable
vmlinux.o: warning: objtool: iovec_from_user+0x88: call to copy_iovec_from_user.part.0() with UACCESS enabled
vmlinux.o: warning: objtool: __import_iovec+0x147: call to copy_iovec_from_user.part.0() with UACCESS enabled
--------------------------------------------------------------------------------
x86_64_defconfig+kselftest (x86_64, clang-16) — PASS, 0 errors, 3 warnings, 0 section mismatches
Warnings:
vmlinux.o: warning: objtool: set_ftrace_ops_ro+0x28: relocation to !ENDBR: .text+0x14252b
vmlinux.o: warning: objtool: set_ftrace_ops_ro+0x3e: relocation to !ENDBR: .text+0x1423b6
vmlinux.o: warning: objtool: lkdtm_UNSET_SMEP+0xca: relocation to !ENDBR: native_write_cr4+0x4
---
For more info write to <info@kernelci.org>
reply other threads:[~2023-05-17 19:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=64652a04.170a0220.4c0ca.32fa@mx.google.com \
--to=bot@kernelci.org \
--cc=kernelci-results@groups.io \
--cc=linux-kselftest@vger.kernel.org \
--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