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
| ||
|
Date: Mon, 25 Feb 2019 12:00:43 +0100 From: Joerg Roedel <jroedel@...e.de> To: Borislav Petkov <bp@...en8.de> Cc: Dave Young <dyoung@...hat.com>, bhe@...hat.com, Jerry Hoemann <jerry.hoemann@....com>, x86@...nel.org, Randy Dunlap <rdunlap@...radead.org>, kexec@...ts.infradead.org, linux-kernel@...r.kernel.org, Pingfan Liu <kernelfans@...il.com>, Mike Rapoport <rppt@...ux.vnet.ibm.com>, Andrew Morton <akpm@...ux-foundation.org>, yinghai@...nel.org, vgoyal@...hat.com, iommu@...ts.linux-foundation.org, konrad.wilk@...cle.com Subject: Re: [PATCHv7] x86/kdump: bugfix, make the behavior of crashkernel=X consistent with kaslr On Fri, Feb 22, 2019 at 02:00:26PM +0100, Borislav Petkov wrote: > On Fri, Feb 22, 2019 at 09:42:41AM +0100, Joerg Roedel wrote: > > The current default of 256MB was found by experiments on a bigger > > number of machines, to create a reasonable default that is at least > > likely to be sufficient of an average machine. > > Exactly, and this is what makes sense. > > The code should try the requested reservation and if it fails, it should > try high allocation with default swiotlb size because we need to reserve > *some* range. Right, makes sense. While at it, maybe it is time to move the default allocation policy to 'high' again. The change was reverted six years ago because it broke old kexec tools, but those are probably out-of-service now. I think this change would make the whole crashdump allocation process less fragile. Regards, Joerg
Powered by blists - more mailing lists