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