diff options
| author | Josh Poimboeuf <jpoimboe@redhat.com> | 2021-01-21 15:29:22 -0600 |
|---|---|---|
| committer | Josh Poimboeuf <jpoimboe@redhat.com> | 2021-01-26 11:12:00 -0600 |
| commit | ecf11ba4d066fe527586c6edd6ca68457ca55cf4 (patch) | |
| tree | ee3fb4bffbc2cf2735b4cba2d3cc14972cff3a6e /net/sctp | |
| parent | 18660698a3d30868524cefb60dcd4e0e297f71bb (diff) | |
| download | linux-stable-ecf11ba4d066fe527586c6edd6ca68457ca55cf4.tar.gz linux-stable-ecf11ba4d066fe527586c6edd6ca68457ca55cf4.tar.bz2 linux-stable-ecf11ba4d066fe527586c6edd6ca68457ca55cf4.zip | |
objtool: Assume only ELF functions do sibling calls
There's an inconsistency in how sibling calls are detected in
non-function asm code, depending on the scope of the object. If the
target code is external to the object, objtool considers it a sibling
call. If the target code is internal but not a function, objtool
*doesn't* consider it a sibling call.
This can cause some inconsistencies between per-object and vmlinux.o
validation.
Instead, assume only ELF functions can do sibling calls. This generally
matches existing reality, and makes sibling call validation consistent
between vmlinux.o and per-object.
Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
Link: https://lore.kernel.org/r/0e9ab6f3628cc7bf3bde7aa6762d54d7df19ad78.1611263461.git.jpoimboe@redhat.com
Diffstat (limited to 'net/sctp')
0 files changed, 0 insertions, 0 deletions