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: Thu, 8 Sep 2022 09:23:07 -0700 From: Dionna Amalie Glaze <dionnaglaze@...gle.com> To: Mike Rapoport <rppt@...ux.ibm.com> Cc: Dave Hansen <dave.hansen@...el.com>, Tom Lendacky <thomas.lendacky@....com>, Mel Gorman <mgorman@...hsingularity.net>, Vlastimil Babka <vbabka@...e.cz>, "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>, Borislav Petkov <bp@...en8.de>, Andy Lutomirski <luto@...nel.org>, Sean Christopherson <seanjc@...gle.com>, Andrew Morton <akpm@...ux-foundation.org>, Joerg Roedel <jroedel@...e.de>, Ard Biesheuvel <ardb@...nel.org>, Andi Kleen <ak@...ux.intel.com>, Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@...ux.intel.com>, David Rientjes <rientjes@...gle.com>, Thomas Gleixner <tglx@...utronix.de>, Peter Zijlstra <peterz@...radead.org>, Paolo Bonzini <pbonzini@...hat.com>, Ingo Molnar <mingo@...hat.com>, Dario Faggioli <dfaggioli@...e.com>, Mike Rapoport <rppt@...nel.org>, David Hildenbrand <david@...hat.com>, Marcelo Cerri <marcelo.cerri@...onical.com>, tim.gardner@...onical.com, Khalid ElMously <khalid.elmously@...onical.com>, philip.cox@...onical.com, "the arch/x86 maintainers" <x86@...nel.org>, Linux Memory Management List <linux-mm@...ck.org>, linux-coco@...ts.linux.dev, linux-efi <linux-efi@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org> Subject: Re: [PATCHv7 02/14] mm: Add support for unaccepted memory > > Looks like the first access to the memory map fails, although I think > it's not in INIT_LIST_HEAD() but rather in init_page_count(). > > I'd start with making sure that page_alloc::memmap_alloc() actually returns > accepted memory. If you build kernel with CONFIG_DEBUG_VM=y the memory map > will poisoned in this function, so my guess is it'd crash there. > That's a wonderful hint, thank you! I did not run this test CONFIG_DEBUG_VM set, but you think it's possible it could still be here? > -- > Sincerely yours, > Mike. -- -Dionna Glaze, PhD (she/her)
Powered by blists - more mailing lists