From: Takashi Iwai <tiwai@suse.de>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Takashi Sakamoto <o-takashi@sakamocchi.jp>,
LKML <linux-kernel@vger.kernel.org>,
alsa-devel@alsa-project.org, lkp@01.org
Subject: Re: [LKP] [ALSA] 3a6d1980fe: kernel_BUG_at_mm/page_alloc.c
Date: Mon, 26 Nov 2018 09:17:32 +0100 [thread overview]
Message-ID: <s5hr2f86yn7.wl-tiwai@suse.de> (raw)
In-Reply-To: <20181126002805.GI18977@shao2-debian>
On Mon, 26 Nov 2018 01:28:05 +0100,
kernel test robot wrote:
>
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 3a6d1980fe96dbbfe3ae58db0048867f5319cdbf ("ALSA: Replace snd_malloc_pages() and snd_free_pages() with standard helpers")
> https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git for-next
....
> [ 174.830284] kernel BUG at mm/page_alloc.c:2850!
OK, this seem to be an issue about using __GFP_COMP and
alloc_pages_exact(). I didn't hit this while testing locally maybe
just because I used the buffer size in power-of-two casually.
I dropped the patch until we sort this out.
thanks,
Takashi
prev parent reply other threads:[~2018-11-26 8:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 0:28 [LKP] [ALSA] 3a6d1980fe: kernel_BUG_at_mm/page_alloc.c kernel test robot
2018-11-26 8:17 ` Takashi Iwai [this message]
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=s5hr2f86yn7.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=o-takashi@sakamocchi.jp \
--cc=rong.a.chen@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).