From: Guenter Roeck <linux@roeck-us.net>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Problems with commit 'kallsyms: add support for relative offsets in kallsyms address table' (in mmotm)
Date: Sat, 23 Jan 2016 20:11:31 -0800 [thread overview]
Message-ID: <56A44EF3.5050504@roeck-us.net> (raw)
In-Reply-To: <56A431B5.8010505@roeck-us.net>
On 01/23/2016 06:06 PM, Guenter Roeck wrote:
> Hi,
>
> I see runtime problems with the current mmotm branch. All qemu mips targets
> (32 and 64 bit, big and little endian) are stuck in boot after this commit.
>
> Bisect points to commit d13682e4d9d2 ("kallsyms: add support for relative offsets
> in kallsyms address table". Disabling CONFIG_KALLSYMS_BASE_RELATIVE fixes the problem,
> ie I can boot the image with qemu.
>
> Bisect log is attached.
>
> Playing with the problem, I found the following:
>
> 1) The problem is only seen with a toolchain using binutils 2.22, but not
> with a toolchain using binutils 2.25. The compiler configuration may be
> different for both toolchains.
> 2) Message "kallsyms failure: absolute symbol value 0xffffffff807afd14 out of range
> in relative mode" (twice) when using the toolchain with binutils 2.22.
> This does not cause the build to fail, though.
> 3) kallsyms_sym_address() parameter variable type is "int". In the calling code,
> the variable type used is "unsigned long". That has no impact on the problem,
> though.
>
More trouble: All sparc32 qemu tests fail, and x86_64 qemu tests fail for images built
with SMP disabled. In all cases, disabling KALLSYMS_BASE_RELATIVE fixes the problem.
Guenter
> Please let me know if there is anything I can do to help tracking down the problem.
>
> Thanks,
> Guenter
>
> ---
> # bad: [437b7ef6d6484bb36afb2c75897e14bf03113dbd] pci: test for unexpectedly disabled bridges
> # good: [afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc] Linux 4.4
> git bisect start 'HEAD' 'v4.4'
> # bad: [10078c1820d81131bc338c7c919feb2638a912ad] ocfs2: o2hb: add NEGOTIATE_APPROVE message
> git bisect bad 10078c1820d81131bc338c7c919feb2638a912ad
> # bad: [1b06048b37e888edb609e1509070ec0c6580eedd] kallsyms-add-support-for-relative-offsets-in-kallsyms-address-table-fix
> git bisect bad 1b06048b37e888edb609e1509070ec0c6580eedd
> # good: [ed312d94332968c86f53295795a3d122fd32cea2] arch/alpha/kernel/systbls.S: remove debug check
> git bisect good ed312d94332968c86f53295795a3d122fd32cea2
> # good: [1cbe7000217b0126821ecd8fba0ba5f9315a0560] thp: limit number of object to scan on deferred_split_scan()
> git bisect good 1cbe7000217b0126821ecd8fba0ba5f9315a0560
> # good: [474324b13e8184aa088c722b771f0f31ab773476] vmstat: remove BUG_ON from vmstat_update
> git bisect good 474324b13e8184aa088c722b771f0f31ab773476
> # good: [d94a9840c248207040d62ca0f380943db9423418] proc: fix missing reference of mm
> git bisect good d94a9840c248207040d62ca0f380943db9423418
> # bad: [d13682e4d9d2ad8220354b5e1a2bd6623e1f2e38] kallsyms: add support for relative offsets in kallsyms address table
> git bisect bad d13682e4d9d2ad8220354b5e1a2bd6623e1f2e38
> # first bad commit: [d13682e4d9d2ad8220354b5e1a2bd6623e1f2e38] kallsyms: add support for relative offsets in kallsyms address table
prev parent reply other threads:[~2016-01-24 4:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 2:06 Problems with commit 'kallsyms: add support for relative offsets in kallsyms address table' (in mmotm) Guenter Roeck
2016-01-24 2:35 ` Guenter Roeck
2016-01-24 6:10 ` Ard Biesheuvel
2016-01-24 7:06 ` Guenter Roeck
2016-01-24 8:21 ` Ard Biesheuvel
2016-01-24 17:05 ` Guenter Roeck
2016-01-24 17:20 ` Ard Biesheuvel
2016-01-24 18:01 ` Guenter Roeck
2016-01-24 19:01 ` Ard Biesheuvel
2016-01-24 19:16 ` Ard Biesheuvel
2016-01-24 4:11 ` Guenter Roeck [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=56A44EF3.5050504@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=heiko.carstens@de.ibm.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
/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