All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Egorenkov <egorenar@linux.ibm.com>
To: Luis Chamberlain <mcgrof@kernel.org>,
	Bruno Goncalves <bgoncalv@redhat.com>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	akpm@linux-foundation.org, bp@alien8.de, corbet@lwn.net,
	gregkh@linuxfoundation.org, jeyu@kernel.org,
	linux-kernel@vger.kernel.org, ndesaulniers@google.com,
	torvalds@linux-foundation.org, Dave Young <dyoung@redhat.com>
Subject: Re: [PATCH v3 1/2] init/initramfs.c: do unpacking asynchronously
Date: Wed, 28 Jul 2021 12:38:08 +0200	[thread overview]
Message-ID: <87pmv2g1v3.fsf@oc8242746057.ibm.com> (raw)
In-Reply-To: <YQAQFMDMk09wS6Qv@bombadil.infradead.org>
In-Reply-To: 

Luis Chamberlain <mcgrof@kernel.org> writes:

> On Tue, Jul 27, 2021 at 09:31:54AM +0200, Bruno Goncalves wrote:
>> On Mon, Jul 26, 2021 at 1:46 PM Rasmus Villemoes
>> <linux@rasmusvillemoes.dk> wrote:
>> >
>> > On 24/07/2021 09.46, Alexander Egorenkov wrote:
>> > > Hello,
>> > >
>> > > since e7cb072eb988 ("init/initramfs.c: do unpacking asynchronously"), we
>> > > started seeing the following problem on s390 arch regularly:
>> > >
>> > > [    5.039734] wait_for_initramfs() called before rootfs_initcalls
>
> So some context here, which might help.
>
> The initramfs_cookie is initialized until a a rootfs_initcall() is
> called, in this case populate_rootfs(). The code is small, so might
> as well include it:
>
> static int __init populate_rootfs(void)
> {
> 	initramfs_cookie = async_schedule_domain(do_populate_rootfs, NULL,
> 						 &initramfs_domain);
> 	if (!initramfs_async)
> 		wait_for_initramfs();
> 	return 0;
> }                                                                               
> rootfs_initcall(populate_rootfs);
>
> The warning you see comes from a situation where a wait_for_initramfs()
> gets called but we haven't yet initialized initramfs_cookie.  There are
> only a few calls for wait_for_initramfs() in the kernel, and the only
> thing I can think of is that somehow s390 may rely on a usermode helper
> early on, but not every time.
>
> What umh calls does s390 issue?
>
>> Unfortunately, we haven't been able to find the root cause, but since
>> June 23rd we haven't hit this panic...
>> 
>> Btw, this panic we were hitting only when testing kernels from "scsi"
>> and "block" trees.
>
> Do you use drdb maybe?
>
>   Luis

You are right, it looks like wait_for_initramfs() is being triggered by drbg:

[    3.396467]  [<00000001f8d917e4>] call_usermodehelper_exec+0x44/0x1c8
[    3.396470]  [<00000001f8da5524>] __request_module+0x17c/0x3d0
[    3.396473]  [<00000001f93b4808>] crypto_alg_mod_lookup+0x228/0x290
[    3.396475]  [<00000001f93b4aae>] crypto_alloc_tfm_node+0x5e/0x158
[    3.396477]  [<00000001f93bbe14>] crypto_alloc_shash+0x34/0x40
[    3.396480]  [<00000001f93d2ee2>] drbg_init_hash_kernel+0x3a/0x100
[    3.396482]  [<00000001f93d306e>] drbg_alloc_state+0xc6/0x280
[    3.396484]  [<00000001f93d33d8>] drbg_kcapi_seed+0x1b0/0x310
[    3.396486]  [<00000001f93d1884>] crypto_rng_reset+0x5c/0xe0
[    3.396488]  [<00000001f93c1750>] alg_test_drbg+0x300/0x478
[    3.396490]  [<00000001f93c0934>] alg_test+0x304/0x530
[    3.396493]  [<00000001f93bedb8>] cryptomgr_test+0x68/0x70
[    3.396495]  [<00000001f8d9f40c>] kthread+0x14c/0x160
[    3.396497]  [<00000001f8d2af14>] __ret_from_fork+0x3c/0x58
[    3.396500]  [<00000001f984c86a>] ret_from_fork+0xa/0x30

Regards
Alex

  parent reply	other threads:[~2021-07-28 10:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-13 21:25 [PATCH v3 0/2] background initramfs unpacking, and CONFIG_MODPROBE_PATH Rasmus Villemoes
2021-03-13 21:25 ` [PATCH v3 1/2] init/initramfs.c: do unpacking asynchronously Rasmus Villemoes
2021-03-15 20:21   ` Luis Chamberlain
2021-03-15 21:33   ` Andrew Morton
2021-03-15 21:59     ` Rasmus Villemoes
2021-07-24  7:46   ` Alexander Egorenkov
2021-07-26 11:46     ` Rasmus Villemoes
2021-07-27  7:31       ` Bruno Goncalves
2021-07-27 13:54         ` Luis Chamberlain
2021-07-27 14:12           ` Bruno Goncalves
2021-07-27 14:21             ` Luis Chamberlain
2021-07-27 14:27               ` Bruno Goncalves
2021-07-27 14:42                 ` Luis Chamberlain
2021-07-27 14:48                   ` Bruno Goncalves
2021-07-28 10:44                   ` Alexander Egorenkov
2021-07-28 10:38           ` Alexander Egorenkov [this message]
2021-07-28 10:36       ` Alexander Egorenkov
2021-07-28 11:49         ` Rasmus Villemoes
2021-03-13 21:25 ` [PATCH v3 2/2] modules: add CONFIG_MODPROBE_PATH Rasmus Villemoes
2021-03-15 20:06   ` Luis Chamberlain
2021-03-15 20:23 ` [PATCH v3 0/2] background initramfs unpacking, and CONFIG_MODPROBE_PATH Luis Chamberlain

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pmv2g1v3.fsf@oc8242746057.ibm.com \
    --to=egorenar@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=bgoncalv@redhat.com \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=dyoung@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jeyu@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=mcgrof@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: [PATCH v3 1/2] init/initramfs.c: do unpacking asynchronously' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.