linux-kernel - Re: [PATCH] rv: Ensure containers are registered first

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: <20250718104018.lyupqBnR@linutronix.de>
Date: Fri, 18 Jul 2025 12:40:18 +0200
From: Nam Cao <namcao@...utronix.de>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Steven Rostedt <rostedt@...dmis.org>,
	Masami Hiramatsu <mhiramat@...nel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	Gabriele Monaco <gmonaco@...hat.com>,
	linux-trace-kernel@...r.kernel.org, linux-kernel@...r.kernel.org,
	stable@...r.kernel.org
Subject: Re: [PATCH] rv: Ensure containers are registered first

On Fri, Jul 18, 2025 at 12:27:14PM +0200, Greg KH wrote:
> On Fri, Jul 18, 2025 at 11:18:50AM +0200, Nam Cao wrote:
> > If rv_register_monitor() is called with a non-NULL parent pointer (i.e. by
> > monitors inside a container), it is expected that the parent (a.k.a
> > container) is already registered.
> > 
> > The containers seem to always be registered first. I suspect because of the
> > order in Makefile. But nothing guarantees this.
> 
> Yes, linking order matters, and it does guarantee this.  We rely on
> linking order in the kernel in many places.

Hmm, I thought this is just how the linker happens to behave, but not a
guarantee.

Let's discard this patch then.

Nam