From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f181.google.com ([209.85.192.181]:33224 "EHLO mail-pf0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751364AbcBZR6I (ORCPT ); Fri, 26 Feb 2016 12:58:08 -0500 Received: by mail-pf0-f181.google.com with SMTP id q63so55531331pfb.0 for ; Fri, 26 Feb 2016 09:58:08 -0800 (PST) Date: Fri, 26 Feb 2016 09:58:06 -0800 From: Omar Sandoval To: Al Viro Cc: linux-fsdevel@vger.kernel.org, Omar Sandoval Subject: Re: [PATCH 0/2] fix RLIMIT_CORE accounting for sparse dumps Message-ID: <20160226175806.GB10341@vader.DHCP.TheFacebook.com> References: <20160226175722.GA10341@vader.DHCP.TheFacebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160226175722.GA10341@vader.DHCP.TheFacebook.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, Feb 26, 2016 at 09:57:22AM -0800, Omar Sandoval wrote: > On Thu, Feb 18, 2016 at 04:32:52PM -0800, Omar Sandoval wrote: > > From: Omar Sandoval > > > > Hi, > > > > Someone here reported that they were getting truncated core dumps even > > when RLIMIT_CORE was larger than the physical memory of the machine. It > > looks some cleanup patches back in v3.13 [1] changed the behaviour of > > the limit to also charge for sparse areas of a file. > [snip] > > > > Omar Sandoval (2): > > coredump: get rid of coredump_params->written > > coredump: only charge written data against RLIMIT_CORE > > > > arch/powerpc/platforms/cell/spufs/coredump.c | 5 +++-- > > fs/binfmt_elf.c | 2 +- > > fs/binfmt_elf_fdpic.c | 2 +- > > fs/coredump.c | 7 ++----- > > 4 files changed, 7 insertions(+), 9 deletions(-) > > > > -- > > 2.7.1 > > > > Ping, any change this can get in for -rc6? > > -- > Omar s/change/chance/ -- Omar