summaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/sun4i/sun4i_framebuffer.h
diff options
context:
space:
mode:
authorHari Bathini <hbathini@linux.ibm.com>2024-11-30 01:56:21 +0530
committerShuah Khan <skhan@linuxfoundation.org>2024-12-11 10:08:04 -0700
commit777f290ab328de333b85558bb6807a69a59b36ba (patch)
tree64aabca6ba1d92b0a6426c4f09d569d699eb2795 /drivers/gpu/drm/sun4i/sun4i_framebuffer.h
parent40384c840ea1944d7c5a392e8975ed088ecf0b37 (diff)
downloadlinux-777f290ab328de333b85558bb6807a69a59b36ba.tar.gz
linux-777f290ab328de333b85558bb6807a69a59b36ba.tar.bz2
linux-777f290ab328de333b85558bb6807a69a59b36ba.zip
selftests/ftrace: adjust offset for kprobe syntax error test
In 'NOFENTRY_ARGS' test case for syntax check, any offset X of `vfs_read+X` except function entry offset (0) fits the criterion, even if that offset is not at instruction boundary, as the parser comes before probing. But with "ENDBR64" instruction on x86, offset 4 is treated as function entry. So, X can't be 4 as well. Thus, 8 was used as offset for the test case. On 64-bit powerpc though, any offset <= 16 can be considered function entry depending on build configuration (see arch_kprobe_on_func_entry() for implementation details). So, use `vfs_read+20` to accommodate that scenario too. Link: https://lore.kernel.org/r/20241129202621.721159-1-hbathini@linux.ibm.com Fixes: 4231f30fcc34a ("selftests/ftrace: Add BTF arguments test cases") Suggested-by: Masami Hiramatsu <mhiramat@kernel.org> Signed-off-by: Hari Bathini <hbathini@linux.ibm.com> Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Diffstat (limited to 'drivers/gpu/drm/sun4i/sun4i_framebuffer.h')
0 files changed, 0 insertions, 0 deletions