On Fri, Feb 26, 2016 at 01:31:08PM -0500, Chris Mason wrote: > 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 <osandov@xxxxxx> > > > > > > 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? > > Since this isn't a recent regression, I'd wait until the next merge > window instead of rc6. > > -chris Al, does this look okay for the merge window? -- Omar -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
