linux-kernel - Re: Runaway loop with the current git.

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ac3eb2510812061956g6bb422d9r7c8032fb68552b4c@mail.gmail.com>
Date:	Sun, 7 Dec 2008 04:56:04 +0100
From:	"Kay Sievers" <kay.sievers@...y.org>
To:	"Evgeniy Polyakov" <zbr@...emap.net>
Cc:	"Alan Cox" <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org
Subject: Re: Runaway loop with the current git.

On Sat, Dec 6, 2008 at 21:26, Evgeniy Polyakov <zbr@...emap.net> wrote:
> On Sat, Dec 06, 2008 at 08:32:06PM +0100, Kay Sievers (kay.sievers@...y.org) wrote:
>> I don't know if it may have any bad side-effects. It moves the tty
>> registration earlier, before we do pci, framebuffer, video, acpi
>> registration.
>>
>> It boots fine here with and without initramfs.
>>
>> Maybe it makes the "dead" /dev/console in your initramfs working, then
>> we at least know the problem.
>
> I will try this patch this Monday and report back the results.

I was able to reproduce it with the .config you attached, and running it in kvm.

It is caused by:
  "modprobe cryptomgr" called from swapper[1]

This modprobe process does try to log an error, accesses /dev/console,
which is not initialized in the kernel at that time, and the kernel
module loader tries the load a module to support dev_t 5:1, which
again runs modprobe, and ...

Setting CONFIG_CRYPTO_MANAGER=y makes it disapper. The patch I sent
seems to fix it.

The bug is handled here: http://bugzilla.kernel.org/show_bug.cgi?id=12153

Thanks,
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/