libhugetlbfs test suite failed with brk_near_huge test

Bug #1653597 reported by Po-Hsu Lin
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Triaged
Undecided
Unassigned
linux (Ubuntu)
Confirmed
Medium
Unassigned
linux-azure (Ubuntu)
Confirmed
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)
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
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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
Revision history for this message
Po-Hsu Lin (cypressyew) wrote : Re: libhugetlbfs test suite failed with brk_near_huge test on GCE with 4.8.0-34.36

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
Revision history for this message
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
Revision history for this message
Kleber Sacilotto de Souza (kleber-souza) wrote :
Revision history for this message
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.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

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

Revision history for this message
Sean Feole (sfeole) wrote :

This appears to be related to Azure giving the context of the bug, tagging as such, next is this still an issue to date? if not, has there been a test generated to test for this specific issue in the future? or can we forget it?

tags: added: kqa-azure
Changed in ubuntu-kernel-tests:
status: New → Incomplete
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Changed in linux-azure (Ubuntu):
status: New → Incomplete
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This issue still exists for 4.15.0-1019.20~16.04.1-gcp [1](every nodes for GCP) and 4.15.0-1022.22~16.04.1-azure [2] (some nodes for Azure)

09/05 13:30:43 ERROR| utils:0153| [stderr] brk_near_huge: malloc.c:2394: 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.

[1] http://10.246.72.7/4.15.0-1019.20~16.04.1-gcp/xenial-linux-gcp-gcp-4.15.0-n1-standard-1-libhugetlbfs/libhugetlbfs/results/libhugetlbfs/debug/libhugetlbfs.DEBUG.html

[2] http://10.246.72.46/-azure/xenial-linux-azure-edge-azure-edge-4.15.0-Standard_DS1-libhugetlbfs/libhugetlbfs/results/libhugetlbfs/debug/libhugetlbfs.DEBUG.html

Changed in ubuntu-kernel-tests:
status: Incomplete → Confirmed
Changed in linux-azure (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
summary: - libhugetlbfs test suite failed with brk_near_huge test on GCE with
- 4.8.0-34.36
+ libhugetlbfs test suite failed with brk_near_huge test on GCP
Revision history for this message
Sean Feole (sfeole) wrote : Re: libhugetlbfs test suite failed with brk_near_huge test on GCP

This issue still exists 4.15.0-1031.32

11/13 20:41:28 DEBUG| utils:0153| [stdout] truncate_above_4GB (2M: 64): PASS
634. 11/13 20:41:28 ERROR| utils:0153| [stderr] brk_near_huge: malloc.c:2394: 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.

http://10.246.72.46/4.15.0-1031.32~16.04.1-azure/xenial-linux-azure-azure-4.15.0-Basic_A0-libhugetlbfs/libhugetlbfs/results/libhugetlbfs/debug/libhugetlbfs.DEBUG.html

Sean Feole (sfeole)
summary: - libhugetlbfs test suite failed with brk_near_huge test on GCP
+ libhugetlbfs test suite failed with brk_near_huge test on GCP & Azure
Sean Feole (sfeole)
tags: added: aws
tags: added: azure gcp
summary: - libhugetlbfs test suite failed with brk_near_huge test on GCP & Azure
+ libhugetlbfs test suite failed with brk_near_huge test
Po-Hsu Lin (cypressyew)
tags: removed: kqa-azure yakkety
Brad Figg (brad-figg)
tags: added: cscc
Sean Feole (sfeole)
tags: added: sru-20190722
Sean Feole (sfeole)
tags: added: 20190812
tags: added: sru-20190812
removed: 20190812
Po-Hsu Lin (cypressyew)
tags: added: libhugetlbfs
Connor Kuehl (connork)
Changed in linux (Ubuntu):
assignee: nobody → Connor Kuehl (connork)
importance: Undecided → Medium
Connor Kuehl (connork)
Changed in linux (Ubuntu):
assignee: Connor Kuehl (connork) → nobody
Revision history for this message
Connor Kuehl (connork) wrote :

I just looked at the test results for this test suite across some GCP cloud instances and it looks like it's failing across the 4.15 kernels.

Changed in ubuntu-kernel-tests:
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.