summaryrefslogtreecommitdiffstats
path: root/fs/locks.c
diff options
context:
space:
mode:
authorJosh Poimboeuf2016-10-13 23:26:15 +0200
committerIngo Molnar2016-10-18 12:21:16 +0200
commit55a76b59b5fef408442e16121faa9eb00a65fd50 (patch)
tree20716520fdd5960572e15f6b0dbac064e7b9ca34 /fs/locks.c
parentLinux 4.9-rc1 (diff)
downloadkernel-qcow2-linux-55a76b59b5fef408442e16121faa9eb00a65fd50.tar.gz
kernel-qcow2-linux-55a76b59b5fef408442e16121faa9eb00a65fd50.tar.xz
kernel-qcow2-linux-55a76b59b5fef408442e16121faa9eb00a65fd50.zip
locking/rwsem/x86: Add stack frame dependency for ____down_write()
Arnd reported the following objtool warning: kernel/locking/rwsem.o: warning: objtool: down_write_killable()+0x16: call without frame pointer save/setup The warning means gcc placed the ____down_write() inline asm (and its call instruction) before the frame pointer setup in down_write_killable(), which breaks frame pointer convention and can result in incorrect stack traces. Force the stack frame to be created before the call instruction by listing the stack pointer as an output operand in the inline asm statement. Reported-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Link: http://lkml.kernel.org/r/1188b7015f04baf361e59de499ee2d7272c59dce.1476393828.git.jpoimboe@redhat.com Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'fs/locks.c')
0 files changed, 0 insertions, 0 deletions