From: Mel Gorman <mgorman@suse.de>
To: Uladzislau Rezki <urezki@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
akpm@linux-foundation.org, hdanton@sina.com, mhocko@suse.com,
mm-commits@vger.kernel.org, npiggin@gmail.com,
oleksiy.avramchenko@sonymobile.com, rostedt@goodmis.org,
willy@infradead.org
Subject: Re: [failures] mm-vmalloc-print-a-warning-message-first-on-failure.patch removed from -mm tree
Date: Thu, 13 May 2021 15:18:58 +0100 [thread overview]
Message-ID: <20210513141858.GM3672@suse.de> (raw)
In-Reply-To: <20210513132418.GA1425@pc638.lan>
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@canb.auug.org.au/
> > >
> > 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
next prev parent reply other threads:[~2021-05-13 14:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 20:29 [failures] mm-vmalloc-print-a-warning-message-first-on-failure.patch removed from -mm tree akpm
2021-05-12 22:56 ` Stephen Rothwell
2021-05-13 10:31 ` Uladzislau Rezki
2021-05-13 11:11 ` Mel Gorman
2021-05-13 12:46 ` Uladzislau Rezki
2021-05-13 13:24 ` Uladzislau Rezki
2021-05-13 14:18 ` Mel Gorman [this message]
[not found] ` <CA+KHdyXwdkosDYk4bKtRLVodrwUJnq3NN39xuRQzKJSPTn7+bQ@mail.gmail.com>
2021-05-13 15:51 ` Mel Gorman
2021-05-13 20:18 ` Uladzislau Rezki
2021-05-14 10:19 ` Mel Gorman
2021-05-14 11:45 ` Uladzislau Rezki
2021-05-14 13:45 ` Mel Gorman
2021-05-14 14:50 ` Uladzislau Rezki
2021-05-14 15:41 ` Mel Gorman
2021-05-14 17:16 ` Uladzislau Rezki
2021-05-16 17:17 ` Mel Gorman
2021-05-16 20:31 ` Uladzislau Rezki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210513141858.GM3672@suse.de \
--to=mgorman@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mm-commits@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=oleksiy.avramchenko@sonymobile.com \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=urezki@gmail.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.