From: Mathieu Malaterre <malat@debian.org>
To: Michal Hocko <mhocko@suse.com>
Cc: linux-mm@kvack.org
Subject: WARNING: CPU: 0 PID: 21 at ../mm/page_alloc.c:4258 __alloc_pages_nodemask+0xa88/0xfec
Date: Sat, 26 May 2018 09:14:35 +0200 [thread overview]
Message-ID: <CA+7wUswp_Sr=hHqi1bwRZ3FE2wY5ozZWZ8Z1BgrFnSAmijUKjA@mail.gmail.com> (raw)
Hi Michal,
For the last couple of days, I am seeing the following appearing in
dmesg (*). I am a happy kmemleak user on an oldish Mac Mini G4
(ppc32), it has been working great. What does this new warning checks:
/*
* All existing users of the __GFP_NOFAIL are blockable, so warn
* of any new users that actually require GFP_NOWAIT
*/
if (WARN_ON_ONCE(!can_direct_reclaim))
goto fail;
Thanks,
(*)
[ 269.038911] WARNING: CPU: 0 PID: 21 at ../mm/page_alloc.c:4258
__alloc_pages_nodemask+0xa88/0xfec
[ 269.038931] Modules linked in: ctr ccm uinput arc4 b43 bcma
mac80211 sha256_generic snd_aoa_codec_toonie cfg80211
snd_aoa_fabric_layout snd_aoa snd_aoa_i2sbus snd_aoa_soundbus snd_pcm
evdev snd_timer snd sg ssb soundcore usb_storage autofs4 ext4
crc32c_generic crc16 mbcache jbd2 fscrypto usbhid ohci_pci ohci_hcd
ehci_pci ehci_hcd usbcore firewire_ohci sd_mod sr_mod cdrom
firewire_core sungem sungem_phy crc_itu_t nls_base usb_common
[ 269.039026] CPU: 0 PID: 21 Comm: kswapd0 Tainted: G W
4.17.0-rc6+ #18
[ 269.039032] NIP: c020e8f8 LR: c020e2e0 CTR: c020b514
[ 269.039038] REGS: dde3b6a0 TRAP: 0700 Tainted: G W
(4.17.0-rc6+)
[ 269.039042] MSR: 00021032 <ME,IR,DR,RI> CR: 22224484 XER: 00000000
[ 269.039056]
GPR00: c020e2e0 dde3b750 df6ab480 00000000 00000001
00000000 00000004 00000040
GPR08: 00000800 22224484 00000040 01ffffff 42224482
00000000 00000040 01011a00
GPR16: c0a864bc 00000040 c0c5a730 01011a00 c0c2f5cc
00000000 00000000 c0c318c4
GPR24: c0c6ba20 00000001 c0a84158 01011a00 c0ce065c
c0a84158 00000000 00000000
[ 269.039118] NIP [c020e8f8] __alloc_pages_nodemask+0xa88/0xfec
[ 269.039124] LR [c020e2e0] __alloc_pages_nodemask+0x470/0xfec
[ 269.039128] Call Trace:
[ 269.039136] [dde3b750] [c020e2e0]
__alloc_pages_nodemask+0x470/0xfec (unreliable)
[ 269.039146] [dde3b820] [c0288c14] new_slab+0x53c/0x970
[ 269.039155] [dde3b880] [c028b61c] ___slab_alloc.constprop.23+0x28c/0x468
[ 269.039163] [dde3b920] [c028c754] kmem_cache_alloc+0x290/0x3dc
[ 269.039177] [dde3b990] [c02a6030] create_object+0x50/0x3d0
[ 269.039185] [dde3b9e0] [c028c7a8] kmem_cache_alloc+0x2e4/0x3dc
[ 269.039193] [dde3ba50] [c0200f88] mempool_alloc+0x7c/0x164
[ 269.039205] [dde3bab0] [c03e33c0] bio_alloc_bioset+0x130/0x298
[ 269.039216] [dde3baf0] [c0278694] get_swap_bio+0x34/0xe8
[ 269.039223] [dde3bb30] [c0278fb4] __swap_writepage+0x22c/0x644
[ 269.039237] [dde3bbb0] [c022528c] pageout.isra.13+0x238/0x52c
[ 269.039246] [dde3bc10] [c02288a0] shrink_page_list+0x9d4/0x1768
[ 269.039254] [dde3bcb0] [c022a264] shrink_inactive_list+0x2c4/0xa34
[ 269.039262] [dde3bd40] [c022b454] shrink_node_memcg+0x344/0xe34
[ 269.039270] [dde3bde0] [c022c068] shrink_node+0x124/0x73c
[ 269.039277] [dde3be50] [c022d78c] kswapd+0x318/0xb2c
[ 269.039291] [dde3bf10] [c008e264] kthread+0x138/0x1f0
[ 269.039300] [dde3bf40] [c001b2e4] ret_from_kernel_thread+0x5c/0x64
[ 269.039304] Instruction dump:
[ 269.039311] 7f44d378 7fa3eb78 4802bd95 4bfff9f4 485d7309 4bfff998
7f03c378 7fc5f378
[ 269.039326] 7f44d378 4802bd79 7c781b78 4bfffd48 <0fe00000> 8081002c
3ca0c08b 7fe6fb78
[ 269.039343] ---[ end trace c255e24f03e28d77 ]---
[ 269.039351] kmemleak: Cannot allocate a kmemleak_object structure
[ 269.039373] kmemleak: Kernel memory leak detector disabled
[ 269.039412] kmemleak: Automatic memory scanning thread ended
next reply other threads:[~2018-05-26 7:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-26 7:14 Mathieu Malaterre [this message]
2018-05-28 8:34 ` Michal Hocko
2018-05-28 13:05 ` [PATCH] kmemleak: don't use __GFP_NOFAIL Tetsuo Handa
2018-05-28 13:24 ` Michal Hocko
2018-05-28 21:05 ` Tetsuo Handa
2018-05-29 13:27 ` Chunyu Hu
2018-05-29 13:46 ` Tetsuo Handa
2018-05-30 9:35 ` Chunyu Hu
2018-05-30 10:46 ` Michal Hocko
2018-05-30 11:42 ` Chunyu Hu
2018-05-30 12:38 ` Michal Hocko
2018-05-31 10:51 ` Chunyu Hu
2018-05-31 11:35 ` Michal Hocko
2018-05-31 12:28 ` Chunyu Hu
2018-05-31 15:22 ` Catalin Marinas
2018-05-31 18:41 ` Michal Hocko
2018-06-01 1:50 ` Chunyu Hu
2018-06-01 4:53 ` Chunyu Hu
2018-06-04 8:41 ` Dmitry Vyukov
2018-06-04 12:42 ` Michal Hocko
2018-06-04 15:08 ` Catalin Marinas
2018-06-04 15:36 ` Dmitry Vyukov
2018-06-04 16:41 ` Catalin Marinas
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='CA+7wUswp_Sr=hHqi1bwRZ3FE2wY5ozZWZ8Z1BgrFnSAmijUKjA@mail.gmail.com' \
--to=malat@debian.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.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