linux-kernel - Re: [PATCH] kexec/kdump: Minor Documentation updates for arm64 and Image

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:   Mon, 22 May 2017 12:09:26 +0530
From:   Pratyush Anand <panand@...hat.com>
To:     AKASHI Takahiro <takahiro.akashi@...aro.org>,
        Dave Young <dyoung@...hat.com>,
        Bharat Bhushan <Bharat.Bhushan@....com>, bhe@...hat.com,
        vgoyal@...hat.com, corbet@....net, kexec@...ts.infradead.org,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kexec/kdump: Minor Documentation updates for arm64 and
 Image



On Friday 19 May 2017 09:15 AM, AKASHI Takahiro wrote:
>>> +to load dump-capture kernel.
>>> +
>>> +   kexec -p <dump-capture-kernel-Image> \
>>> +   --initrd=<initrd-for-dump-capture-kernel> \
>>> +   --append="root=<root-dev> <arch-specific-options>"
>> For uncompressed Image, dtb is not necessary?
> Just for clarification, dtb is optional for both vmlinux and Image
> on arm64. (This means you can specify it if you want.)
> But this is also true for initrd and append(command line) to some extent.

Yes, I agree.
>
> More precisely, whether these parameters are optional or not will
> depend on architectures, not formats, I believe.

May be not architecture, rather a distro environment.

For example, we should be able to work without --initrd for any arch if kernel 
has been compiled by configuring CONFG_INITRAMFS_SOURCE.

~Pratyush