diff options
| author | Josh Poimboeuf <[email protected]> | 2019-07-18 01:36:46 +0000 |
|---|---|---|
| committer | Thomas Gleixner <[email protected]> | 2019-07-18 19:01:06 +0000 |
| commit | a7e47f26039c26312a4144c3001b4e9fa886bd45 (patch) | |
| tree | 5cd47870c750d1701946c8d9cbd51448b8b0f1fe /tools/perf/scripts/python/mem-phys-addr.py | |
| parent | bpf: Disable GCC -fgcse optimization for ___bpf_prog_run() (diff) | |
| download | kernel-a7e47f26039c26312a4144c3001b4e9fa886bd45.tar.gz kernel-a7e47f26039c26312a4144c3001b4e9fa886bd45.zip | |
objtool: Add mcsafe_handle_tail() to the uaccess safe list
After an objtool improvement, it's reporting that __memcpy_mcsafe() is
calling mcsafe_handle_tail() with AC=1:
arch/x86/lib/memcpy_64.o: warning: objtool: .fixup+0x13: call to mcsafe_handle_tail() with UACCESS enabled
arch/x86/lib/memcpy_64.o: warning: objtool: __memcpy_mcsafe()+0x34: (alt)
arch/x86/lib/memcpy_64.o: warning: objtool: __memcpy_mcsafe()+0xb: (branch)
arch/x86/lib/memcpy_64.o: warning: objtool: __memcpy_mcsafe()+0x0: <=== (func)
mcsafe_handle_tail() is basically an extension of __memcpy_mcsafe(), so
AC=1 is supposed to be set. Add mcsafe_handle_tail() to the uaccess
safe list.
Signed-off-by: Josh Poimboeuf <[email protected]>
Signed-off-by: Thomas Gleixner <[email protected]>
Tested-by: Nick Desaulniers <[email protected]>
Acked-by: Peter Zijlstra (Intel) <[email protected]>
Link: https://lkml.kernel.org/r/035c38f7eac845281d3c3d36749144982e06e58c.1563413318.git.jpoimboe@redhat.com
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions