libhugetlbfs test suite failed with brk_near_huge test on GCE with 4.8.0-34.36

Bug #1653597 reported by Po-Hsu Lin on 2017-01-03
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned
linux-azure (Ubuntu)
Undecided
Unassigned

Bug Description

Kernel: 4.8.0-34.36

The libhugetlbfs failed with the brk_near_huge test on x86_64(gce)

12/24 04:59:42 DEBUG| utils:0153| [stdout] truncate_above_4GB (2M: 64): PASS
12/24 04:59:42 ERROR| utils:0153| [stderr] brk_near_huge: malloc.c:2403: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.
12/24 04:59:42 DEBUG| utils:0153| [stdout] brk_near_huge (2M: 64):
12/24 04:59:42 DEBUG| utils:0153| [stdout] task-size-overrun (2M: 64): PASS

Full log: http://pastebin.ubuntu.com/23732201/

Po-Hsu Lin (cypressyew) on 2017-01-03
summary: - libhugetlbfs failed with brk_near_huge test on GCE with 4.8.0-34.36
+ libhugetlbfs test suite failed with brk_near_huge test on GCE with
+ 4.8.0-34.36

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1653597

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Po-Hsu Lin (cypressyew) wrote :

This failure can be found on Xenial kernel 4.4.0-58.79 on gce as well.

http://pastebin.ubuntu.com/23732791/

tags: added: xenial
Po-Hsu Lin (cypressyew) wrote :

I can't collect information as I don't have access to cloud instances yet.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Seth Forshee (sforshee) wrote :

Also seen on 4.11 in artful. The assertion seems to be related to internal heap bookkeeping, so likely a glibc error or heap corruption and not a kernel problem.

Po-Hsu Lin (cypressyew) wrote :

For the record, it's found on linux-azure 4.11.0-1003 as well.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers