linux-kernel - Re: [PATCH] LoongArch: KVM: Move kvm_iocsr tracepoint out of generic code

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

Message-ID: <CAAhV-H7KYEU-N42w8O-4BdPmDWtFOVYGmHrzyNvvnPePFg2xbw@mail.gmail.com>
Date: Fri, 29 Aug 2025 18:14:03 +0800
From: Huacai Chen <chenhuacai@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Bibo Mao <maobibo@...ngson.cn>, LKML <linux-kernel@...r.kernel.org>, 
	Linux Trace Kernel <linux-trace-kernel@...r.kernel.org>, kvm@...r.kernel.org, 
	loongarch@...ts.linux.dev, Tianrui Zhao <zhaotianrui@...ngson.cn>, 
	Paolo Bonzini <pbonzini@...hat.com>, Masami Hiramatsu <mhiramat@...nel.org>, 
	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Subject: Re: [PATCH] LoongArch: KVM: Move kvm_iocsr tracepoint out of generic code

On Wed, Aug 20, 2025 at 9:35 PM Steven Rostedt <rostedt@...dmis.org> wrote:
>
> On Wed, 20 Aug 2025 11:03:05 +0800
> Huacai Chen <chenhuacai@...nel.org> wrote:
>
> > > Did this fall through the cracks?
> > I don't know what this means, but I think you are pinging.
>
> Sorry for the colloquialism, it's not actually the same as a ping. A ping
> is for something that had no response. This is more about the patch was
> acknowledged but did not go further. "Falling through the cracks" is like
> picking a bunch of things up with a bucket that has a crack in it. Some of
> those things may "fall through the crack" and not be processed.
> >
> > This patch appears after I sent the KVM PR for 6.17, and it isn't a
> > bugfix, so it will go to 6.18.
>
> Well, it will start causing warnings soon because it wastes memory. But
> that will likely begin in 6.18 so we are OK, as long as it gets into
> linux-next before the warning trigger does.
Applied, thanks.

Huacai

>
> -- Steve
>