linux-kernel - initramfs size & crashkernel reserved area

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

Message-ID: <BANLkTin7FZLkjqY1-Z_7DvQRgrFe3zYtwQ@mail.gmail.com>
Date:	Tue, 21 Jun 2011 15:01:05 -0700
From:	Sujit V <sujit.linux@...il.com>
To:	linux-kernel@...r.kernel.org, kexec@...ts.infradead.org
Subject: initramfs size & crashkernel reserved area

I am observing the following.

We are using linux 2.6.23 kernel
crashkernel=128M@16M

We also have few kernel modules in our code base.

The kernel modules are gzip'ed in the cpio archive which is included
in the .init.ramfs section of vmlinux

When the size of the .init.ramfs section goes beyond certain limit
then it corrupts the crash kernel reserved area.

If the .init.ramfs size is 0x33d0f6 then things work ok.

If the init.ramfs size is 0x4be430 then it corrupts the crashkernel area.

Any pointers for further debugging?
--
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/