linux-kernel - Re: [PATCH v2] trace, RAS: Use __print_symbolic helper for entry severity for aer

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250414163347.GEZ_0461mT0OZGpOjl@fat_crate.local>
Date: Mon, 14 Apr 2025 18:33:47 +0200
From: Borislav Petkov <bp@...en8.de>
To: Sargun Dhillon <sargun@...gun.me>, Steven Rostedt <rostedt@...dmis.org>
Cc: linux-kernel@...r.kernel.org, linux-edac@...r.kernel.org,
	"Paul E . McKenney" <paulmck@...nel.org>,
	Tony Luck <tony.luck@...el.com>
Subject: Re: [PATCH v2] trace, RAS: Use __print_symbolic helper for entry
 severity for aer_events

+ Rostedt.

On Mon, Apr 14, 2025 at 08:38:34AM -0700, Sargun Dhillon wrote:
> The chained ternary conditional operator in the perf event format for
> ras:aer_event was causing a misrepresentation of the severity of the event
> when used with "perf script". Rather than building our own hand-rolled
> formatting, just use the __print_symbolic helper to format it.
> 
> Specifically, all corrected errors were being formatted as non-fatal,
> uncorrected errors, as shown below with the BAD_TLP errors, which is
> correctable. This is due to a bug in libtraceevent, where chained
> ternary conditions are not parsed correctly.

So because *some* libtraceevent has a bug, we're wagging the dog, not the
tail?

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette