From: Andrew Morton <akpm@linux-foundation.org>
To: sedat.dilek@gmail.com
Cc: linux-mm <linux-mm@kvack.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [v3.17-rc8] LTP oom testsuite produces OOPS
Date: Tue, 25 Mar 2014 08:56:09 -0700 [thread overview]
Message-ID: <20140325085609.9132a2e1.akpm@linux-foundation.org> (raw)
In-Reply-To: <CA+icZUUr2Wua1kNoB1oCje2rU0KQx5c+V6A76UP0c99gg6UxTg@mail.gmail.com>
On Tue, 25 Mar 2014 08:45:34 +0100 Sedat Dilek <sedat.dilek@gmail.com> wrote:
> Hi,
>
> as reported in [1] in my post-scriptum I see several OOPs when running
> LTP and OOM tests (here: oom3).
> Linus requested to send you mm-folks my bug-report.
>
> # cd /opt/ltp/
>
> # cat Version
> 20140115
>
> # ./testcases/bin/oom03
>
> I have tested with latest LTP (15-Jan-2014).
>
> If you need additional information, please let me know.
I don't actually see any oopses there. There are some stack traces
associated with the oom-killing events:
[ 104.383349] Memory cgroup out of memory: Kill process 2518 (oom03) score 777 or sacrifice child
[ 104.383352] Killed process 2518 (oom03) total-vm:3152196kB, anon-rss:1048444kB, file-rss:192kB
[ 107.946908] oom03 invoked oom-killer: gfp_mask=0xd0, order=0, oom_score_adj=0
[ 107.946912] oom03 cpuset=/ mems_allowed=0
[ 107.946915] CPU: 0 PID: 2521 Comm: oom03 Not tainted 3.14.0-rc8-1-iniza-small #1
[ 107.946917] Hardware name: SAMSUNG ELECTRONICS CO., LTD. 530U3BI/530U4BI/530U4BH/530U3BI/530U4BI/530U4BH, BIOS 13XK 03/28/2013
[ 107.946919] ffff880108e58400 ffff880064125be8 ffffffff8170fb45 0000000000000007
[ 107.946923] ffff880108e7a190 ffff880064125c68 ffffffff8170c6e5 ffff880064125cd8
[ 107.946925] ffff88010b686858 ffff88011fdf9d80 ffff88010b6863d0 0000000000000000
[ 107.946928] Call Trace:
[ 107.946934] [<ffffffff8170fb45>] dump_stack+0x46/0x58
[ 107.946937] [<ffffffff8170c6e5>] dump_header+0x7e/0x1c3
[ 107.946942] [<ffffffff813881e0>] ? ___ratelimit+0xa0/0x120
[ 107.946946] [<ffffffff811580e4>] oom_kill_process+0x214/0x370
[ 107.946949] [<ffffffff81075ce5>] ? has_ns_capability_noaudit+0x15/0x20
...
But these aren't oopses - mm/oom_kill.c:dump_header() deliberately
performs a dump_stack() while reporting on the event.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-03-25 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 7:45 Sedat Dilek
2014-03-25 15:56 ` Andrew Morton [this message]
2014-03-25 20:31 ` Sedat Dilek
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=20140325085609.9132a2e1.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sedat.dilek@gmail.com \
--cc=torvalds@linux-foundation.org \
/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