Re: [PATCH] x86/kprobes: Fix boundary check in insn_jump_into_range()

From: Dave Hansen

Date: Thu Nov 19 2026 - 19:41:15 EST


On 11/19/26 16:36, Jinke Han wrote:
> Since there is no reported failure, I'm fine with dropping the Fixes:
> tag if you'd prefer to treat this as a cleanup. I can also post a
> separate change that makes the check use the actual optimized length
> instead of the open-coded DISP32_SIZE, if you think that's the better
> direction, and add a regression case under
> tools/testing/selftests/kprobes.

The Fixes: is fine, but it would be nice to have a better changelog
about what's going on.

Not voluminous, just better, please.