linux-kernel - Re: [2.6.22-rc4] kexec failed: invalid argument

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: <m1hcpanlkw.fsf@ebiederm.dsl.xmission.com>
Date:	Thu, 14 Jun 2007 17:49:19 -0600
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	caglar@...dus.org.tr
Cc:	linux-kernel@...r.kernel.org, horms@...ge.net.au
Subject: Re: [2.6.22-rc4] kexec failed: invalid argument

"S.Çağlar Onur" <caglar@...dus.org.tr> writes:

> Hi;
>
> With current Linus's git tree + current kexec-tools-testing [1] (also with 
> kexec-tools-1.101) tree "kexec -e" call on reboot failed with following;
>
> kexec failed: invalid argument
>
> kexec document says its users responsibility to close running softwares, 
> mounting disks in read only mode etc. and it suggest calling "kexec -e" just 
> before the "reboot" call and talks about future merge with sysvinit's reboot 
> and kexec, and when i did it, it will not starts new kernel and instead gaves 
> that error.
>
> But more supringuisly if i try to execute "kexec -e" directly (in init3 with 
> rw disks and lots of running software) it will starts new kernel without a 
> problem. 
>
> For reference im using following kexec line for loading the kernel
> kexec -l /boot/kernel-2.6.22-rc4-CFS-v16 --append="root=/dev/sda3"
> --initrd=/boot/initramfs-2.6.22-rc4-CFS-v16
>
> I'm not sure this is a regression or my(maybe me or kexec document misses some 
> point) mistake cause this is my first attempt to use kexec, but i want to 
> report the situation :)
>
>  [1] 
> http://git.kernel.org/?p=linux/kernel/git/horms/kexec-tools-testing.git;a=summary

Sight unseen I'm guessing that you have a kexec aware distro that is doing
something in the runlevel change scripts and thus unloading the kernel.
What do: /sys/kernel/kexec_loaded and /sys/kernel/kexec_crash_loaded say?

kexec -e at any point should start a loaded kernel without problems, but it is
a lot like pressing the reset button.  Nothing is guaranteed to be shutdown
cleanly.  Now that journalling filesystems are the norm it is quite possible
nothing bad will happen to you.

Eric
-
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/