linux-kernel - Re: Re: [PATCH 1/1 v1] the recommended crash memory reservation is too small for x86

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: <1cd75ef.b411.13da1646593.Coremail.yizhouzhou@ict.ac.cn>
Date:	Mon, 25 Mar 2013 19:52:24 +0800 (GMT+08:00)
From:	周洲仪 <yizhouzhou@....ac.cn>
To:	"WANG Chao" <chaowang@...hat.com>
Cc:	zhouzhouyi@...il.com, kexec@...ts.infradead.org,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	vgoyal@...hat.com
Subject: Re: Re: [PATCH 1/1 v1] the recommended crash memory reservation is
 too small for x86_64.

Thanks for reviewing
  Is it sounds good to add following line into section "Boot into System Kernel":

  The memory reserved for crash kernel should be no less than the unpacked init ram disk size
that loaded with dump-capture kernel plus wired memory used by kernel itself.

  #################
  After all, I have been trapped into "hang after capture" problem when sticking strictly to this document.
Cheers
Zhouyi  

> 
> On 03/25/2013 06:56 PM, zhouzhouyi@...il.com wrote:
> > From: root <root@...-Lenovo.(none)>
> > 
> > 
> >  On Documentation/kdump/kdump.txt, section Boot into  System Kernel: On x86 and x86_64, use
> >  "crashkernel=64M@16M", but some OSes like ubuntu 12.10 use ram fs larger than 64M, so in these cases the
> >  memory reserved for crashkernel should be at least 128M.
> 
> People use different initramfs generators for different purpose. That means
> the size of initramfs and also its memory consuming can vary very much from
> each other. You just can't list all these generators and their recommended
> reserved memory here. Though I have to say crashkernel=128M is good choice.
> 
> I think it would be better to leave this to user or distribution itself to
> determine how much memory should be reserved for crash kernel, then export
> this value to kernel in some ways.
> 
> Thanks,
> WANG Chao
> 
> > 
> > 
> > Signed-off-by: Zhouyi Zhou <yizhouzhou@....ac.cn>
> > ---
> >  Documentation/kdump/kdump.txt |    4 +++-
> >  1 file changed, 3 insertions(+), 1 deletion(-)
> > 
> > diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt
> > index 13f1aa0..1e850e0 100644
> > --- a/Documentation/kdump/kdump.txt
> > +++ b/Documentation/kdump/kdump.txt
> > @@ -290,7 +290,9 @@ Boot into System Kernel
> >     "crashkernel=64M@16M" tells the system kernel to reserve 64 MB of memory
> >     starting at physical address 0x01000000 (16MB) for the dump-capture kernel.
> >  
> > -   On x86 and x86_64, use "crashkernel=64M@16M".
> > +   On x86 and x86_64, use "crashkernel=64M@16M" (some OSes use init ram fs larger
> > +than 64M, for example ubuntu-12.10, use crashkernel=128M@16M instead, or dump-capture
> > +kernel will out of memory).
> >  
> >     On ppc64, use "crashkernel=128M@32M".
> >  
> > 
> 




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