Re: [failures] mm-vmalloc-print-a-warning-message-first-on-failure.patch removed from -mm tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, May 13, 2021 at 03:24:18PM +0200, Uladzislau Rezki wrote:
> > > > What can of testing failures does it trigger? Where can i find the
> > > > details, logs or tracers of it?
> > > 
> > > https://lore.kernel.org/linux-next/20210512175359.17793d34@xxxxxxxxxxxxxxxx/
> > > 
> > Thanks, Mel.
> > 
> > OK. Now i see. The problem is with this patch:
> > 
> > mm/vmalloc: switch to bulk allocator in __vmalloc_area_node()
> > 
> > <SNIP>
> > 
> > So during the boot process when the module is about to be loaded, the vmalloc allocation
> > gets failed in the __alloc_pages_bulk(). 
> > 
> > Will try to reproduce. It would be good to get a kernel config.
> > Appreciate for any thoughts about it?
> > 
> 
> I see that on the target machine when the problem occurs the PAGE_SIZE is 64K. 
> 
> Can it be somehow connected to it? Also one question, just guessing, the crash
> happens during the boot, therefore the question is: is __alloc_pages_bulk()
> fully initialized by that time? 
> 

A boot test on KVM using my distribution config (openSUSE Leap 15.2)
failed on x86-64 so it's not related to PAGE_SIZE.

-- 
Mel Gorman
SUSE Labs



[Index of Archives]     [Kernel Archive]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]

  Powered by Linux