linux-kernel - uprobe_events can't accept paths that contain spaces

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CAGqt0zxtKboY1PWRN4kCF3uTeiH9ZJtj280ARvGWeNtR_ik0eQ@mail.gmail.com>
Date: Fri, 22 Nov 2024 00:42:51 +0000
From: Yuxuan Shui <yshuiv7@...il.com>
To: linux-trace-kernel@...r.kernel.org
Cc: Steven Rostedt <rostedt@...dmis.org>, Masami Hiramatsu <mhiramat@...nel.org>, 
	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, open list <linux-kernel@...r.kernel.org>
Subject: uprobe_events can't accept paths that contain spaces

Hi,

I hit this problem accidentally when one of the shared libraries I was
looking at is located in a directory with spaces in its name. `perf
probe` reported "Failed to write event: Invalid argument".

If I understand the code correctly, strings written into uprobe_events
are strictly splitted at whitespaces (by `argv_split`). This seems
like an unfortunate restriction. If I submit a patch to introduce
support for either quotes (") or escapes (\), will that be considered?

(For context I am running something that expects its libraries to be
located at fixed paths, so moving them to a different path would be
awkward at best.)

Thanks.

-- 

Regards
Yuxuan Shui