All of lore.kernel.org
 help / color / mirror / Atom feed
From: Serge Hallyn <serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
To: Aaron Staley <aaron-ZNH+RosXeVlBDgjK7y7TUQ@public.gmane.org>
Cc: Paul Menage <menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
	Li Zefan <lizf-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>,
	"containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
	<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: PROBLEM: Processes writing large files in memory-limited LXC container are killed by OOM
Date: Mon, 1 Jul 2013 10:21:50 -0500	[thread overview]
Message-ID: <20130701152150.GA4078@sergelap> (raw)
In-Reply-To: <CAMcjixZdXWGezcVQPPo3M0yNBx4TtbiOoqYJQWvNbTyqULifUA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Quoting Aaron Staley (aaron-ZNH+RosXeVlBDgjK7y7TUQ@public.gmane.org):
> The behavior it fixes sounds similar to what I'm seeing. However, if I read
> the logs correctly, wasn't this committed into Linux 3.5? If so, wouldn't
> Linux 3.8.0-25-generic #37-Ubuntu SMP (where I can reproduce the problem)
> already have this fix?

Hi,

I've been trying to reproduce this in ubuntu raring, but couldn't.  I
started a shell as unprivileged user, and stuck it in a memory cgroup
with memory.limit_in_bytes set to 10M.  Did dd if=/dev/zero of=/tmp/xxx
bs=1M count=100M - it was slow, and memory.failcnt hit 1612526, but it
did in the end succeed.

kernel here is 3.8.0-23-generic #34-Ubuntu, slightly older than you.
Maybe you're onto a new regression?

-serge

  parent reply	other threads:[~2013-07-01 15:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25  5:45 PROBLEM: Processes writing large files in memory-limited LXC container are killed by OOM Aaron Staley
     [not found] ` <CAMcjixYa-mjo5TrxmtBkr0MOf+8r_iSeW5MF4c8nJKdp5m+RPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-25 13:24   ` Serge Hallyn
2013-06-25 20:54     ` Aaron Staley
     [not found]       ` <CAMcjixZtW0KdAmLXyDoGFqL2qh4aEgdGjBYJWrPESFMz0dvELw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-27  5:12         ` Zhu Yanhai
     [not found]           ` <CAC8teKXNof5PdU2dMz4iZ8tM=Dx=aZ0efxotDhdc-xopeK-+Xg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-27  5:19             ` Aaron Staley
     [not found]               ` <CAMcjixZdXWGezcVQPPo3M0yNBx4TtbiOoqYJQWvNbTyqULifUA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-27 20:51                 ` Aristeu Rozanski
2013-07-01 15:21                 ` Serge Hallyn [this message]
2013-07-01 15:27                   ` Aaron Staley
2013-06-28 18:52         ` Serge E. Hallyn
2013-07-01 18:01   ` Serge Hallyn
2013-07-01 18:01     ` Serge Hallyn
2013-07-01 18:01     ` Serge Hallyn
2013-07-01 18:45     ` Johannes Weiner
2013-07-01 18:45     ` Johannes Weiner
2013-07-01 18:45       ` Johannes Weiner
2013-07-01 18:51       ` Aaron Staley
     [not found]       ` <20130701184503.GG17812-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
2013-07-01 18:51         ` Aaron Staley
2013-07-01 19:02         ` Serge Hallyn
2013-07-01 19:02           ` Serge Hallyn
2013-07-01 19:02           ` Serge Hallyn
2013-07-02 12:42           ` Michal Hocko
2013-07-02 12:42             ` Michal Hocko
2013-07-02 12:42             ` Michal Hocko

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=20130701152150.GA4078@sergelap \
    --to=serge.hallyn-gewih/nmzzlqt0dzr+alfa@public.gmane.org \
    --cc=aaron-ZNH+RosXeVlBDgjK7y7TUQ@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=lizf-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org \
    --cc=menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.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.