linux-kernel - bug: keep_bootcon and early printk together can lead to (invisible) kernel panic

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-next>] [day] [month] [year] [list]

Message-ID: <20130221153717.31400a88.pkluba@dension.com>
Date:	Thu, 21 Feb 2013 15:37:17 +0100
From:	"Patrik, Kluba" <pkluba@...sion.com>
To:	linux-mips@...ux-mips.org
Cc:	linux-kernel@...r.kernel.org
Subject: bug: keep_bootcon and early printk together can lead to (invisible)
 kernel panic

Hi!

I had a silent lockup on one of our embedded system under development.
It was not easy to track it down, so here's what I discovered, in case
somebody runs into similar trouble.
Using 'keep_bootcon' command line parameter, and enabling early printk
can lead to a kernel panic. At least on MIPS, it does. The problem is
that in arch/mips/kernel/early_printk.c everything is declared as
__init and __initdata, so they are being freed, when the kernel
frees .init.* sections. If 'keep_bootcon' is given, the early console
does not get unregistered, and the entry in the console_drivers list
can point (will, believe me) to garbage data. It's up to you to imagine
the effects...

Regards,
Patrik

--
Patrik KLUBA
Software Developer at

DENSION Audio Systems Ltd.
H-1116 Budapest, Sztregova u. 1
Phone: +36 1 463 0470
Fax:   +36 1 463 0479
Web:   www.dension.com
--
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/