[PATCH v3] powerpc/xmon: Fix tmpstr length check in scanhex

[Michael Ellerman]

On Mon, 26 Aug 2024 12:12:17 +0530, Madhavan Srinivasan wrote:
> If a function name is greater than 63 char long, xmon command
> may not find them. For example, here is a test that
> executed an illegal instruction in a kernel function and one of
> call stack function has name >63 char long,
> 
> cpu 0x0: Vector: 700 (Program Check) at [c00000000a6577e0]
>     pc: c0000000001aacb8: check__allowed__function__name__for__symbol__r4+0x8/0x10
>     lr: c00000000019c1e0: check__allowed__function__name__for__symbol__r1+0x20/0x40
>     sp: c00000000a657a80
>    msr: 800000000288b033
>   current = 0xc00000000a439900
>   paca    = 0xc000000003e90000	 irqmask: 0x03	 irq_happened: 0x01
> .....
> [link register   ] c00000000019c1e0 check__allowed__function__name__for__symbol__r1+0x20/0x40
> [c00000000a657a80] c00000000a439900 (unreliable)
> [c00000000a657aa0] c0000000001021d8 check__allowed__function__name__for__symbol__r2_resolution_symbol+0x38/0x4c
> [c00000000a657ac0] c00000000019b424 power_pmu_event_init+0xa4/0xa50
> 
> [...]

Applied to powerpc/next.

[1/1] powerpc/xmon: Fix tmpstr length check in scanhex
      https://git.kernel.org/powerpc/c/0405e128110d47a40443936e68dc32d7bc4ccc0b

cheers