All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: objtool warning breaks build for fs/dlm/lock.o
Date: Wed, 6 May 2020 16:07:25 +0200	[thread overview]
Message-ID: <CAK8P3a0QkqyA2wq_EbA+oWrLGgVdQwpBvb+G0aKyz60BOLs6fg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2156 bytes --]

Hi,

During randconfig testing with clang-10 I came across a number
of additional objtool warnings, I'll send another mail about those
when I have collected more information and some object files.

This one sticks out however, as objtool returns an error code that
stops the build:

$ make V=1 2>&1 | tail
clang-10 -Wp,-MMD,fs/dlm/.lock.o.d  -nostdinc -isystem
/usr/lib/llvm-10/lib/clang/10.0.1/include
-I/git/arm-soc/arch/x86/include -I./arch/x86/include/generated
-I/git/arm-soc/include -I./include
-I/git/arm-soc/arch/x86/include/uapi
-I./arch/x86/include/generated/uapi -I/git/arm-soc/include/uapi
-I./include/generated/uapi -include
/git/arm-soc/include/linux/kconfig.h -include
/git/arm-soc/include/linux/compiler_types.h -D__KERNEL__ -Wall -Wundef
-Werror=strict-prototypes -fno-strict-aliasing -fno-common
-fshort-wchar -fno-PIE -Werror=implicit-function-declaration
-Werror=implicit-int -std=gnu89 --target=x86_64-linux
--prefix=/home/arnd/cross/x86_64/gcc-10.0.20200413-nolibc/x86_64-linux/bin/
--gcc-toolchain=/home/arnd/cross/x86_64/gcc-10.0.20200413-nolibc/x86_64-linux
-no-integrated-as -Werror=unknown-warning-option -mno-sse -mno-mmx
-mno-sse2 -mno-3dnow -mno-avx -m64 -mno-80387 -mstack-alignment=8
-mtune=generic -mno-red-zone -mcmodel=kernel -DCONFIG_X86_X32_ABI
-Wno-sign-compare -fno-asynchronous-unwind-tables
-fno-delete-null-pointer-checks -O2 -Wframe-larger-than=2048
-fno-stack-protector -fno-omit-frame-pointer
-fno-optimize-sibling-calls -mno-omit-leaf-frame-pointer
-Wdeclaration-after-statement -Wvla -fno-strict-overflow
-fno-merge-all-constants -fno-stack-check -Werror=date-time
-Werror=incompatible-pointer-types -fmacro-prefix-map=/git/arm-soc/=
-Werror  -I /git/arm-soc/fs/dlm -I ./fs/dlm
-DKBUILD_MODFILE='"fs/dlm/dlm"' -DKBUILD_BASENAME='"lock"'
-DKBUILD_MODNAME='"dlm"' -c -o fs/dlm/lock.o
/git/arm-soc/fs/dlm/lock.c
   ./tools/objtool/objtool check  --uaccess fs/dlm/lock.o
fs/dlm/lock.o: warning: objtool: __receive_convert_reply()+0x1e5:
can't find jump dest instruction at .text+0xcaa7
make[4]: *** [/git/arm-soc/scripts/Makefile.build:273: fs/dlm/lock.o] Error 255

Attached object file and .config.

      Arnd

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 38681 bytes --]

[-- Attachment #3: lock.o.gz --]
[-- Type: application/gzip, Size: 31418 bytes --]

             reply	other threads:[~2020-05-06 14:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 14:07 Arnd Bergmann [this message]
2020-05-07 23:29 ` objtool warning breaks build for fs/dlm/lock.o Josh Poimboeuf
2020-05-08  9:27   ` Arnd Bergmann
2020-05-08  9:55     ` Peter Zijlstra
2020-05-08 16:17       ` Josh Poimboeuf
2020-05-08 16:26         ` Peter Zijlstra
2020-05-08 16:29           ` Josh Poimboeuf
2020-05-08  9:45   ` Peter Zijlstra
2020-05-08 16:20     ` Josh Poimboeuf
2020-05-18 19:57   ` Arnd Bergmann
2020-05-18 22:53     ` Josh Poimboeuf
2020-05-18 23:04       ` Josh Poimboeuf

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=CAK8P3a0QkqyA2wq_EbA+oWrLGgVdQwpBvb+G0aKyz60BOLs6fg@mail.gmail.com \
    --to=arnd@arndb.de \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.