linux-kernel - 2.6.31-rc6: WARNING: at mm/page_alloc.c:1805 __alloc_pages

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Fri, 6 Nov 2009 21:10:49 -0200
From:	Rogério Brito <rbrito@....usp.br>
To:	linux-kernel@...r.kernel.org
Cc:	tytso@....edu, Mel Gorman <mel@....ul.ie>,
	Rik van Riel <riel@...hat.com>, Ingo Molnar <mingo@...e.hu>
Subject: 2.6.31-rc6: WARNING: at mm/page_alloc.c:1805 __alloc_pages_nodemas

Hi, Ted.

I am getting some stack traces (since the inclusion of commit
4b4f278c030aa4b6ee0915f396e9a9478d92d610) as follows:

,----
| [    6.449029] Adding 3903784k swap on /dev/hda2.  Priority:-1 extents:1 across:3903784k 
| [    6.638766] ------------[ cut here ]------------
| [    6.638842] WARNING: at mm/page_alloc.c:1805 __alloc_pages_nodemask+0x15e/0x57e()
| [    6.638913] Hardware name:  
| [    6.638962] Modules linked in: snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm firewire_ohci snd_timer firewire_core i2c_i801 snd e100 8139too mii uhci_hcd ehci_hcd fan usbcore parport_pc 8250_pnp crc_itu_t nls_base soundcore snd_page_alloc evdev psmouse rng_core parport 8250 thermal serial_core processor floppy
| [    6.640230] Pid: 898, comm: mount Not tainted 2.6.32-rc6-1-00026-g91d3f9b #1
| [    6.640282] Call Trace:
| [    6.640333]  [<ffffffff8107a169>] ? __alloc_pages_nodemask+0x15e/0x57e
| [    6.640387]  [<ffffffff8107a169>] ? __alloc_pages_nodemask+0x15e/0x57e
| [    6.640441]  [<ffffffff8103dbc8>] ? warn_slowpath_common+0x77/0xa3
| [    6.640495]  [<ffffffff8107a169>] ? __alloc_pages_nodemask+0x15e/0x57e
| [    6.640550]  [<ffffffff810b50d1>] ? alloc_inode+0x3d/0x74
| [    6.640602]  [<ffffffff810b329b>] ? __d_lookup+0x115/0x127
| [    6.640655]  [<ffffffff8107a59b>] ? __get_free_pages+0x12/0x4f
| [    6.640709]  [<ffffffff811396a8>] ? match_number+0x2a/0x8f
| [    6.640762]  [<ffffffff810fcb1f>] ? parse_options+0x474/0x4ed
| [    6.640815]  [<ffffffff810ff4d6>] ? ext4_remount+0xc9/0x34d
| [    6.640868]  [<ffffffff810a4e4c>] ? do_remount_sb+0x8e/0xc3
| [    6.640921]  [<ffffffff810b8f43>] ? do_mount+0x25d/0x777
| [    6.640973]  [<ffffffff810b75e2>] ? copy_mount_options+0xd8/0x13b
| [    6.641033]  [<ffffffff810b94e1>] ? sys_mount+0x84/0xc7
| [    6.641087]  [<ffffffff8100af6b>] ? system_call_fastpath+0x16/0x1b
| [    6.641139] ---[ end trace b9aacc99567ffbb9 ]---
| [    6.836225] iTCO_vendor_support: vendor-support=0
| [    6.842398] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05
`----

This happens when I'm mounting an ext4 fs with the option auto_da_alloc,
but not when I mount without it.

My current mount options are the following:

    rw,relatime,nobarrier,delalloc,max_batch_time=50000,errors=remount-ro

and the filesystem has journal=writeback (I suspect that this may be the
bit that doesn't play nice with auto_da_alloc).

I don't really need auto_da_alloc (or, at least, think that I don't :-)
), but I just wanted to report this.

If any further information is needed, just let me know.


Regards,

-- 
Rogério Brito : rbrito@...ckenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/