mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
synced 2026-05-10 15:13:44 -04:00
5cffad0a5c8f0cc53ce9fe7cff7bc67c3a97c406
Feng Yang says: ==================== libbpf: Fix event name too long error and add tests From: Feng Yang <yangfeng@kylinos.cn> Hi everyone, This series tries to fix event name too long error and add tests. When the binary path is excessively long, the generated probe_name in libbpf exceeds the kernel's MAX_EVENT_NAME_LEN limit (64 bytes). This causes legacy uprobe event attachment to fail with error code -22. The fix reorders the fields to place the unique ID before the name. This ensures that even if truncation occurs via snprintf, the unique ID remains intact, preserving event name uniqueness. Additionally, explicit checks with MAX_EVENT_NAME_LEN are added to enforce length constraints. Acked-by: Jiri Olsa <jolsa@kernel.org> --- Changes in v5: - use strrchr instead of basename. - kprobe_test add __weak. Thanks, Andrii Nakryiko! - Link to v4: https://lore.kernel.org/all/20250415093907.280501-1-yangfeng59949@163.com/ Changes in v4: - add changelog. - gen_uprobe_legacy_event_name and gen_kprobe_legacy_event_name are combined into a function - kprobe_test use normal module function. Thanks, Jiri Olsa! - Link to v3: https://lore.kernel.org/bpf/20250414093402.384872-1-yangfeng59949@163.com/ Changes in v3: - add __sync_fetch_and_add(&index) and let snprintf() do the trimming. Thanks, Andrii Nakryiko! - add selftests. - Link to v2: https://lore.kernel.org/all/20250411080545.319865-1-yangfeng59949@163.com/ Changes in v2: - Use basename() and %.32s to fix. Thanks, Hengqi Chen! - Link to v1: https://lore.kernel.org/all/20250410052712.206785-1-yangfeng59949@163.com/ ==================== Link: https://patch.msgid.link/20250417014848.59321-1-yangfeng59949@163.com Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Merge tag 'asoc-fix-v6.15-rc1' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus
Linux kernel
============
There are several guides for kernel developers and users. These guides can
be rendered in a number of formats, like HTML and PDF. Please read
Documentation/admin-guide/README.rst first.
In order to build the documentation, use ``make htmldocs`` or
``make pdfdocs``. The formatted documentation can also be read online at:
https://www.kernel.org/doc/html/latest/
There are various text files in the Documentation/ subdirectory,
several of them using the reStructuredText markup notation.
Please read the Documentation/process/changes.rst file, as it contains the
requirements for building and running the kernel, and information about
the problems which may result by upgrading your kernel.
Description
Languages
C
97%
Assembly
1%
Shell
0.6%
Rust
0.5%
Python
0.4%
Other
0.3%