public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] min_free_kbytes.c:134: FAIL: child unexpectedly failed: 139
Date: Mon, 17 Feb 2020 09:28:03 -0500 (EST)	[thread overview]
Message-ID: <1121671987.7831869.1581949683671.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <MAXPR0101MB1468DB8754551B9C84AF3C0CEE160@MAXPR0101MB1468.INDPRD01.PROD.OUTLOOK.COM>

[adding back LTP list to CC]

----- Original Message -----
> //***************************   This is the result of strace -f
> 
> 
> pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e18a08000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e18908000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e18808000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e18708000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e18608000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e18508000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e18408000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e18308000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e18208000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e18108000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e18008000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e17f08000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e17e08000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e17d08000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e17c08000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e17b08000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e17a08000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e17908000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e17808000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e17708000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e17608000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e17508000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e17408000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e17308000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e17208000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e17108000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e17008000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e16f08000
> [pid 48522] mmap(NULL, 1048576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3e16e08000
> Segmentation fault

Ok, so we are in eatup_mem loop. mmap() suceeded, and then we seem to crash
on write to allocated area via memset(). My guess would be kernel bug.

To double-check, can you capture a core file and see where exactly child hits SIGSEGV?

> root@exaleapsemi:~/pankaj_ltp_new/ltp/testcases/kernel/mem/tunable#
> min_free_kbytes.c:173: FAIL: child unexpectedly failed: 11
> mem.c:817: INFO: set min_free_kbytes to 163644
> memfree is 8048240 kB before eatup mem
> min_free_kbytes.c:173: FAIL: child unexpectedly failed: 11
> mem.c:817: INFO: set overcommit_memory to 1
> mem.c:817: INFO: set min_free_kbytes to 327288
> memfree is 8047972 kB before eatup mem
> min_free_kbytes.c:155: FAIL: child unexpectedly failed: 11
> mem.c:817: INFO: set min_free_kbytes to 654576
> memfree is 8047800 kB before eatup mem
> min_free_kbytes.c:155: FAIL: child unexpectedly failed: 11
> mem.c:817: INFO: set min_free_kbytes to 163644
> memfree is 8039996 kB before eatup mem
> min_free_kbytes.c:155: FAIL: child unexpectedly failed: 11
> min_free_kbytes.c:103: PASS: min_free_kbytes test pass
> mem.c:817: INFO: set min_free_kbytes to 327288
> mem.c:817: INFO: set overcommit_memory to 1
> 
> Summary:
> passed   1
> failed   7
> skipped  0
> warnings 0


  parent reply	other threads:[~2020-02-17 14:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 12:13 [LTP] min_free_kbytes.c:134: FAIL: child unexpectedly failed: 139 Pankaj Vinadrao Joshi
2020-02-17 11:56 ` Jan Stancek
     [not found]   ` <MAXPR0101MB1468A92491FB531F33F10A36EE160@MAXPR0101MB1468.INDPRD01.PROD.OUTLOOK.COM>
2020-02-17 12:24     ` Jan Stancek
     [not found]       ` <MAXPR0101MB1468DB8754551B9C84AF3C0CEE160@MAXPR0101MB1468.INDPRD01.PROD.OUTLOOK.COM>
2020-02-17 14:28         ` Jan Stancek [this message]
     [not found] ` <MAXPR0101MB14685FEB7F52C97C8835B106EE110@MAXPR0101MB1468.INDPRD01.PROD.OUTLOOK.COM>
     [not found]   ` <558576867.8097569.1582098912792.JavaMail.zimbra@redhat.com>
     [not found]     ` <BM1PR0101MB14596D9D318FF13C32724A32EE100@BM1PR0101MB1459.INDPRD01.PROD.OUTLOOK.COM>
     [not found]       ` <732362668.8105497.1582103304747.JavaMail.zimbra@redhat.com>
     [not found]         ` <MAXPR0101MB1468CAB5F98BE95E3170E7A3EEED0@MAXPR0101MB1468.INDPRD01.PROD.OUTLOOK.COM>
     [not found]           ` <641229800.8775991.1582616022386.JavaMail.zimbra@redhat.com>
     [not found]             ` <MAXPR0101MB14681EB0C7F8BBC970B19ED9EEED0@MAXPR0101MB1468.INDPRD01.PROD.OUTLOOK.COM>
2020-02-25  8:31               ` Jan Stancek
2020-02-25 10:03                 ` Pankaj Vinadrao Joshi

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=1121671987.7831869.1581949683671.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=ltp@lists.linux.it \
    /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