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]
Date:	Sun, 26 Jan 2014 16:00:16 +0100
From:	Richard Weinberger <richard@....at>
To:	Harald Arnesen <skogtun.linux@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Panic with latest git kernel

Am 26.01.2014 15:47, schrieb Harald Arnesen:
> Richard Weinberger [2014-01-26 14:36]:
> 
>>> $ cpio --list </boot/initrd.img-3.13.0-03477-gdf32e43
>>> kernel
>>> kernel/x86
>>> kernel/x86/microcode
>>> kernel/x86/microcode/GenuineIntel.bin
>>> 50 blocks
>>> $
> 
>> Looks very strange.
>> Add rdinit=/bin/sh to your commandline such that you get a shell within
>> the initrd...
> 
> Okay, I did. On the non-working kernel/initrd, the working ditto, and
> the Debian-provided files. And ls shows contents that seem sane.
> 
> None of the initrds have a switch_root in them, neither in /sbin or
> anywhere else. They all have a /bin/pivot_root, which may be the same?

Your image shows that the kernel looses the init process because /init seems
to be unable to exec switch_root.
Find out what is going on in your initrd.

So far it has zero to do with the kernel itself.

Thanks,
//richard
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ