linux-ext4 - Re: [Bug 14562] New: On umount warn in page_alloc.c:1751 __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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091109024443.GD7592@mit.edu>
Date:	Sun, 8 Nov 2009 21:44:43 -0500
From:	Theodore Tso <tytso@....edu>
To:	bugzilla-daemon@...zilla.kernel.org
Cc:	linux-ext4@...r.kernel.org
Subject: Re: [Bug 14562] New: On umount warn in page_alloc.c:1751
	__alloc_pages_slowpath

On Sun, Nov 08, 2009 at 10:52:59PM +0000, bugzilla-daemon@...zilla.kernel.org wrote:
> 
> Created a new ext4 fs on sda5.
> Did copy my backup (about 40Gig back) und did a umount to the fs.
> After this i got this warning:

Did you also do a mount operation shortly afterwards?  It looks like 4
seconds after the unmount completed, it was a mount operation that
caused the warning.

> [43805.914995] EXT4-fs: mballoc: 6643657 preallocated, 1203082 discarded
> [43809.377291] ------------[ cut here ]------------
> [43809.377320] WARNING: at /build/buildd/linux-2.6.31/mm/page_alloc.c:1751

The EXT4-fs: mballoc: is the last line you would normally expect to
see when unmounting the filesystem.  And the warning took place 4
seconds later, which is a eternity as far as kernel-time is
considered.

Also, look at the bottom of the call trace:

> [43809.377512] Call Trace:
> [43809.377531]  [<c014518d>] warn_slowpath_common+0x6d/0xa0
  	....
> [43809.377633]  [<c01e088f>] __kmalloc+0xdf/0x180
> [43809.377646]  [<c031974e>] match_number+0x2e/0xa0
> [43809.377657]  [<c03197ea>] match_int+0xa/0x10
> [43809.377670]  [<c0274102>] parse_options+0x152/0x810
  	....
> [43809.377760]  [<c027baa0>] ? ext4_fill_super+0x0/0x1900
> [43809.377772]  [<c01e9cde>] vfs_kern_mount+0x5e/0x120
> [43809.377784]  [<c01e9df9>] do_kern_mount+0x39/0xd0
> [43809.377797]  [<c01fee2e>] do_new_mount+0x6e/0xa0
> [43809.377808]  [<c01ff7f9>] do_mount+0x1c9/0x1e0
> [43809.377819]  [<c01ff876>] sys_mount+0x66/0xa0
  		  	       ^^^^^^^^^
> [43809.377831]  [<c010336c>] syscall_call+0x7/0xb
> [43809.377840] ---[ end trace a7919e7f17c0a727 ]---


Looks like this was some kind of "interesting" set of mount options
passed to the kernel.  Any chance you could figure out what the mount
options were to the mount operation?

					- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html