linux-kernel - Re: [PATCH v3] perf trace: avoid garbage when not printing a trace event's arguments

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: <173091258725.804318.6915912692367845597.b4-ty@kernel.org>
Date: Wed, 06 Nov 2024 09:03:07 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: acme@...nel.org, Benjamin Peterson <benjamin@...flow.com>
Cc: adrian.hunter@...el.com, alexander.shishkin@...ux.intel.com, 
 howardchu95@...il.com, irogers@...gle.com, jolsa@...nel.org, 
 kan.liang@...ux.intel.com, linux-kernel@...r.kernel.org, 
 linux-perf-users@...r.kernel.org, mark.rutland@....com, mingo@...hat.com, 
 peterz@...radead.org
Subject: Re: [PATCH v3] perf trace: avoid garbage when not printing a trace
 event's arguments

On Sun, 03 Nov 2024 20:48:16 +0000, Benjamin Peterson wrote:

> trace__fprintf_tp_fields may not print any tracepoint arguments. E.g., if the
> argument values are all zero. Previously, this would result in a totally
> uninitialized buffer being passed to fprintf, which could lead to garbage on the
> console. Fix the problem by passing the number of initialized bytes fprintf.
> 
> 

Applied to perf-tools-next, thanks!

Best regards,
Namhyung