From: holgerschurig@gmail.com (Holger Schurig)
To: linux-arm-kernel@lists.infradead.org
Subject: 4.4.3: OOPS when running "stress-ng --sock 5"
Date: Mon, 07 Mar 2016 10:12:55 +0100 [thread overview]
Message-ID: <87fuw2d52g.fsf@gmail.com> (raw)
In-Reply-To: <87twkmd6or.fsf@gmail.com> (Holger Schurig's message of "Fri, 04 Mar 2016 08:48:52 +0100")
I compared my config with imx_v6_v7_defconfig which didn't segfault.
After I turned on CONFIG_SWAP, my segfault vanished.
I did turn off CONFIG_SWAP because my device only has SD-Card and eMMC.
So I never intended to create a swap partition. And thought "why compile
it in the kernel when I never use it?".
But it seems the kernel is instable with this setting.
So we have a potential denial-of-service in kernels compiled without
CONFIG_SWAP, don't we? At least when it comes to skb handling.
Other memory tests never showed anything weird, and my system is running
X11 with some Qt applications as well as Java applications since about a
year without trouble. During all this time without CONFIG_SWAP.
next prev parent reply other threads:[~2016-03-07 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 7:48 4.4.3: OOPS when running "stress-ng --sock 5" Holger Schurig
2016-03-04 15:56 ` Holger Schurig
2016-03-07 10:59 ` Tetsuo Handa
2016-03-07 9:12 ` Holger Schurig [this message]
2016-03-07 9:59 ` Holger Schurig
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=87fuw2d52g.fsf@gmail.com \
--to=holgerschurig@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).