linux-kernel - Re: [PATCH] perf trace: Increase syscall handler map size to 1024

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <176219241991.1981113.12013271209381654543.b4-ty@kernel.org>
Date: Mon, 03 Nov 2025 09:53:39 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: Arnaldo Carvalho de Melo <acme@...nel.org>, 
 Ian Rogers <irogers@...gle.com>, Kan Liang <kan.liang@...ux.intel.com>, 
 Namhyung Kim <namhyung@...nel.org>
Cc: Jiri Olsa <jolsa@...nel.org>, Adrian Hunter <adrian.hunter@...el.com>, 
 Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...nel.org>, 
 LKML <linux-kernel@...r.kernel.org>, linux-perf-users@...r.kernel.org, 
 Howard Chu <howardchu95@...il.com>
Subject: Re: [PATCH] perf trace: Increase syscall handler map size to 1024

On Mon, 19 May 2025 16:25:39 -0700, Namhyung Kim wrote:
> The syscalls_sys_{enter,exit} map in augmented_raw_syscalls.bpf.c has
> max entries of 512.  Usually syscall numbers are smaller than this but
> x86 has x32 ABI where syscalls start from 512.
> 
> That makes trace__init_syscalls_bpf_prog_array_maps() fail in the middle
> of the loop when it accesses those keys.  As the loop iteration is not
> ordered by syscall numbers anymore, the failure can affect non-x32
> syscalls.
> 
> [...]
Applied to perf-tools-next, thanks!

Best regards,
Namhyung