From: Jiri Slaby <jslaby@suse.cz>
To: Andy Lutomirski <luto@amacapital.net>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>
Subject: .gnu.hash into text PHDR?
Date: Tue, 17 Nov 2015 15:12:28 +0100 [thread overview]
Message-ID: <564B35CC.3050803@suse.cz> (raw)
Hi,
after
commit 6b7e26547fad7ace3dcb27a5babd2317fb9d1e12
Author: Andy Lutomirski <luto@amacapital.net>
Date: Thu Aug 6 14:45:45 2015 -0700
x86/vdso: Emit a GNU hash
I believe .gnu.hash in arch/x86/entry/vdso/vdso-layout.lds.S should have
":text", right?
Not that it would matter (it is put there automagically), but I noted it
while hunting a new failure inside KVM (host is 4.2 for some time, guest
was upgraded to 4.3 recently). KVM dies when javac invokes gtod:
KVM internal error. Suberror: 1
emulation failure
...
[javac] # C [linux-vdso.so.1+0xe45] __vdso_gettimeofday+0x125
which is "movl hpet_page+240(%rip), %eax". Any ideas?
More details at:
https://bugzilla.novell.com/show_bug.cgi?id=954218
thanks,
--
js
suse labs
next reply other threads:[~2015-11-17 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 14:12 Jiri Slaby [this message]
2015-11-18 16:14 ` .gnu.hash into text PHDR? Andy Lutomirski
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=564B35CC.3050803@suse.cz \
--to=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=x86@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