summaryrefslogtreecommitdiff
path: root/security
diff options
context:
space:
mode:
authorAlexei Starovoitov <ast@kernel.org>2025-01-20 09:43:29 -0800
committerAlexei Starovoitov <ast@kernel.org>2025-01-20 09:47:17 -0800
commit3f3c2f0cf669ff28b995b3d6b820ab870c2aa9d9 (patch)
tree9b3a227d026d6b2eb96fe789b792099353f03310 /security
parentd10cafc5d54a0f70681ab2f739ea6c46282c86f9 (diff)
parent14a627fe794a10cf507861e63cf9d46077699337 (diff)
downloadlinux-3f3c2f0cf669ff28b995b3d6b820ab870c2aa9d9.tar.gz
linux-3f3c2f0cf669ff28b995b3d6b820ab870c2aa9d9.tar.bz2
linux-3f3c2f0cf669ff28b995b3d6b820ab870c2aa9d9.zip
Merge branch 'bpf-allow-may_goto-0-instruction'
Yonghong Song says: ==================== Emil Tsalapatis from Meta reported such a case where 'may_goto 0' insn is generated by clang-19 compiler and this caused verification failure since 'may_goto 0' is rejected by verifier. In fact, 'may_goto 0' insn is actually a no-op and it won't hurt verification. The only side effect is that the verifier will convert the insn to a sequence of codes like /* r10 - 8 stores the implicit loop count */ r11 = *(u64 *)(r10 -8) if r11 == 0x0 goto pc+2 r11 -= 1 *(u64 *)(r10 -8) = r11 With this patch set 'may_goto 0' insns are allowed in verification which also removes those insns. Changelogs: v1 -> v2: - Instead of a separate function, removing 'may_goto 0' in existing func opt_remove_nops(). ==================== Link: https://patch.msgid.link/20250118192019.2123689-1-yonghong.song@linux.dev Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions