All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Davies <richard@arachsys.com>
To: cgroups@vger.kernel.org, linux-mm@kvack.org, linux-btrfs@vger.kernel.org
Subject: Re: Kernel crash triggered by dd to file with memcg, worst on btrfs
Date: Wed, 16 Apr 2014 18:58:37 +0100	[thread overview]
Message-ID: <20140416175837.GA9412@alpha.arachsys.com> (raw)
In-Reply-To: <20140416174210.GA11486@alpha.arachsys.com>

Richard Davies wrote:
> I have a test case in which I can often crash an entire machine by running
> dd to a file with a memcg with relatively generous limits. This is
> simplified from real world problems with heavy disk i/o inside containers.
>
> The crashes are easy to trigger when dding to create a file on btrfs. On
> ext3, typically there is just an error in the kernel log, although
> occasionally it also crashes.

A further note - the ext3 SLUB errors occur when dding into a ext3 file
alone. The few ext3 crashes occurred when dding into a btrfs file for a
while without a crash, then switching to dding into an ext3 file. So the
"ext3 crashes" could actually be due to btrfs cached data still in memory -
i.e. all crashes could be due to btrfs use.

Richard.

--
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>

WARNING: multiple messages have this Message-ID (diff)
From: Richard Davies <richard@arachsys.com>
To: cgroups@vger.kernel.org, linux-mm@kvack.org, linux-btrfs@vger.kernel.org
Subject: Re: Kernel crash triggered by dd to file with memcg, worst on btrfs
Date: Wed, 16 Apr 2014 18:58:37 +0100	[thread overview]
Message-ID: <20140416175837.GA9412@alpha.arachsys.com> (raw)
In-Reply-To: <20140416174210.GA11486@alpha.arachsys.com>

Richard Davies wrote:
> I have a test case in which I can often crash an entire machine by running
> dd to a file with a memcg with relatively generous limits. This is
> simplified from real world problems with heavy disk i/o inside containers.
>
> The crashes are easy to trigger when dding to create a file on btrfs. On
> ext3, typically there is just an error in the kernel log, although
> occasionally it also crashes.

A further note - the ext3 SLUB errors occur when dding into a ext3 file
alone. The few ext3 crashes occurred when dding into a btrfs file for a
while without a crash, then switching to dding into an ext3 file. So the
"ext3 crashes" could actually be due to btrfs cached data still in memory -
i.e. all crashes could be due to btrfs use.

Richard.

  parent reply	other threads:[~2014-04-16 17:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 17:42 Kernel crash triggered by dd to file with memcg, worst on btrfs Richard Davies
2014-04-16 17:42 ` Richard Davies
2014-04-16 17:58 ` Marian Marinov
2014-04-16 17:58   ` Marian Marinov
     [not found]   ` <534EC4C8.1090106-NV7Lj0SOnH0@public.gmane.org>
2014-04-16 18:05     ` Richard Davies
2014-04-16 18:05       ` Richard Davies
2014-04-16 18:05       ` Richard Davies
2014-04-16 17:58 ` Richard Davies [this message]
2014-04-16 17:58   ` Richard Davies
     [not found] ` <20140416174210.GA11486-2oeHp4OYwSjPZs67QiJbJtBPR1lH4CV8@public.gmane.org>
2014-04-23 21:58   ` Michal Hocko
2014-04-23 21:58     ` Michal Hocko
2014-04-23 21:58     ` Michal Hocko
2014-04-24 10:59     ` Richard Davies
2014-04-24 10:59       ` Richard Davies
2014-04-24 12:26       ` Michal Hocko
2014-04-24 12:26         ` Michal Hocko
2014-04-24 12:19     ` Vladimir Davydov
2014-04-24 12:19       ` Vladimir Davydov

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=20140416175837.GA9412@alpha.arachsys.com \
    --to=richard@arachsys.com \
    --cc=cgroups@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.