linux-kernel - Re: warning: objtool: ...: call without frame pointer save/setup; return with modified stack frame

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20170817165347.z4ipxyglu5vvocr2@treble>
Date:   Thu, 17 Aug 2017 11:53:47 -0500
From:   Josh Poimboeuf <jpoimboe@...hat.com>
To:     Meelis Roos <mroos@...ux.ee>, Ingo Molnar <mingo@...nel.org>
Cc:     Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: warning: objtool: ...: call without frame pointer save/setup;
 return with modified stack frame

On Thu, Aug 17, 2017 at 04:09:58PM +0300, Meelis Roos wrote:
> Today I coticed the following objtool warnings when compiling 
> 4.13-rc5+git for my Atom 330 PC:
> 
> call without frame pointer save/setup
> return with modified stack frame
> 
> Examples (there is a lot more of them in practice):
> 
> arch/x86/kernel/smpboot.o: warning: objtool: arch_update_cpu_topology()+0x29: call without frame pointer save/setup
> arch/x86/kernel/smpboot.o: warning: objtool: native_smp_prepare_cpus()+0x530: return with modified stack frame
> 
> mm/vmalloc.o: warning: objtool: __get_vm_area()+0x26: call without frame pointer save/setup
> mm/vmalloc.o: warning: objtool: get_vm_area()+0x34: call without frame pointer save/setup
> 
> fs/debugfs/inode.o: warning: objtool: debugfs_initialized()+0x22: call without frame pointer save/setup
> fs/debugfs/inode.o: warning: objtool: debugfs_create_file()+0x20: call without frame pointer save/setup
> fs/debugfs/inode.o: warning: objtool: debugfs_create_file_unsafe()+0x20: call without frame pointer save/setup
> 
> mm/nobootmem.o: warning: objtool: __alloc_memory_core_early()+0xb2: return with modified stack frame

Hi Meelis,

Thanks for reporting this issue.  This has been already been fixed in
the tip tree with the following commit:

  5b8de48e82ba ("objtool: Fix '-mtune=atom' decoding support in objtool 2.0")

Ingo, would you be willing to put this patch in the 4.13 urgent queue?

-- 
Josh