From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-fsdevel-owner@vger.kernel.org>
Received: from mail-pf0-f171.google.com ([209.85.192.171]:35942 "EHLO
	mail-pf0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752075AbcBZR5Z (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Fri, 26 Feb 2016 12:57:25 -0500
Received: by mail-pf0-f171.google.com with SMTP id e127so55861030pfe.3
        for <linux-fsdevel@vger.kernel.org>; Fri, 26 Feb 2016 09:57:24 -0800 (PST)
Date: Fri, 26 Feb 2016 09:57:22 -0800
From: Omar Sandoval <osandov@osandov.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, Omar Sandoval <osandov@fb.com>
Subject: Re: [PATCH 0/2] fix RLIMIT_CORE accounting for sparse dumps
Message-ID: <20160226175722.GA10341@vader.DHCP.TheFacebook.com>
References: <cover.1455841898.git.osandov@fb.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <cover.1455841898.git.osandov@fb.com>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

On Thu, Feb 18, 2016 at 04:32:52PM -0800, Omar Sandoval wrote:
> From: Omar Sandoval <osandov@fb.com>
> 
> 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