Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Heiner Kallweit <hkallweit1@gmail.com>
To:     Rasmus Villemoes <linux@rasmusvillemoes.dk>,
        Luis Chamberlain <mcgrof@kernel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
References: <c197724b-3d16-45bd-d71b-0a016196ca40@gmail.com>
Subject: Re: wait_for_initramfs warning from kernel_init_freeable()
Message-ID: <4d6aa2dd-92df-4f36-10ac-cd003a0229f7@gmail.com>
Date:   Thu, 29 Apr 2021 09:16:18 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <c197724b-3d16-45bd-d71b-0a016196ca40@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Precedence: bulk

On 29.04.2021 08:46, Heiner Kallweit wrote:
> Since 97f8172f9a98 ("init/initramfs.c: do unpacking asynchronously") I get
> the following warning early in the boot process from umh:
> "wait_for_initramfs() called before rootfs_initcalls"
> Some debugging lead me to the following call chain:
> 
> kernel_init_freeable()
> -> do_basic_setup()
>    -> driver_init()
>       -> platform_bus_init()
>          -> bus_register()
>             -> kset_register()
>                -> kobject_uvent()
> 

Sorry, this is the first umh call, but at this time UMH_DISABLED is still set.
The first umh call where UMH is enabled is the following:

kernel_init_freeable()
-> do_basic_setup()
   -> do_initcalls()
      -> do_one_initcall()
         -> wq_sysfs_init()         <- core_initcall()
            -> subsys_virtual_register()
               -> bus_register()