linux-kernel - Re: [PATCH] pwm: Make info in traces about affected pwm more useful

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: <20240730103910.6de49acf@gandalf.local.home>
Date: Tue, 30 Jul 2024 10:39:10 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Uwe Kleine-König <u.kleine-koenig@...libre.com>
Cc: Masami Hiramatsu <mhiramat@...nel.org>, Mathieu Desnoyers
 <mathieu.desnoyers@...icios.com>, linux-pwm@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org
Subject: Re: [PATCH] pwm: Make info in traces about affected pwm more useful

On Tue, 30 Jul 2024 09:22:53 +0200
Uwe Kleine-König <u.kleine-koenig@...libre.com> wrote:

> I think the patch is obvious enough to be ok even without the tracing
> maintainer's blessing. I applied it to
> https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git pwm/for-next
> .

No problem. Thanks for the Cc. I don't always reply if the patch is pretty
straight forward. But I do look for things like holes in the TP_struct()
portion, that would waste ring buffer space. As well as uses of
dereferencing pointers.

-- Steve