From: Ingo Molnar <mingo@kernel.org>
To: Elena Reshetova <elena.reshetova@intel.com>,
Andy Lutomirski <luto@kernel.org>
Cc: luto@kernel.org, linux-kernel@vger.kernel.org,
luto@amacapital.net, jpoimboe@redhat.com, keescook@chromium.org,
jannh@google.com, enrico.perla@intel.com, mingo@redhat.com,
bp@alien8.de, tglx@linutronix.de, peterz@infradead.org,
gregkh@linuxfoundation.org
Subject: Re: [PATCH 1/1] x86/entry/64: randomize kernel stack offset upon syscall
Date: Wed, 10 Apr 2019 13:42:59 +0200 [thread overview]
Message-ID: <20190410114259.GB9293@gmail.com> (raw)
In-Reply-To: <20190410112103.15170-2-elena.reshetova@intel.com>
* Elena Reshetova <elena.reshetova@intel.com> wrote:
> 2) Andy's tests, misc-tests: ./timing_test_64 10M sys_enosys
> base: 10000000 loops in 1.62224s = 162.22 nsec / loop
> random_offset (prandom_u32() every syscall): 10000000 loops in 1.64660s = 166.26 nsec / loop
Stupid question, how did you manage to buil timing_test_64? Here it fails
with a bog standard gcc 7.3.0 x86-64 distro toolchain:
dagon:~/luto-misc-tests.git> make timing_test_64
g++ -m64 -o timing_test_64 -O2 -g -std=gnu++11 -pthread -Wall timing_test.cc -lrt -ldl
/usr/bin/ld: /tmp/cc8VRkuV.o: relocation R_X86_64_32S against `.text.startup' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: final link failed: Nonrepresentable section on outputcollect2: error: ld returned 1 exit status
Makefile:39: recipe for target 'timing_test_64' failed
I'm using cb7f9f0592f8, which is like 1.5 years old - is this still the
latest and greatest:
git://git.kernel.org/pub/scm/linux/kernel/git/luto/misc-tests.git
?
Thanks,
Ingo
next prev parent reply other threads:[~2019-04-10 11:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 11:21 [PATCH 0/1] v2, randomize stack offset upon syscall Elena Reshetova
2019-04-10 11:21 ` [PATCH 1/1] x86/entry/64: randomize kernel " Elena Reshetova
2019-04-10 11:42 ` Ingo Molnar [this message]
2019-04-10 14:26 ` Reshetova, Elena
2019-04-10 14:48 ` Andy Lutomirski
2019-04-10 16:20 ` Kees Cook
2019-04-16 7:27 ` Ingo Molnar
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=20190410114259.GB9293@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=elena.reshetova@intel.com \
--cc=enrico.perla@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jannh@google.com \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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