From mboxrd@z Thu Jan 1 00:00:00 1970 From: Serge Hallyn 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 Message-ID: <20130701152150.GA4078@sergelap> References: <20130625132432.GA4098@sergelap> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Aaron Staley Cc: Paul Menage , Li Zefan , "containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org" List-Id: containers.vger.kernel.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