public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: Al Viro <viro@zeniv.linux.org.uk>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-team@fb.com, Omar Sandoval <osandov@fb.com>
Subject: [PATCH RESEND v3 0/2] fix RLIMIT_CORE accounting for sparse dumps
Date: Wed, 11 May 2016 15:16:35 -0700	[thread overview]
Message-ID: <cover.1463004510.git.osandov@fb.com> (raw)

From: Omar Sandoval <osandov@fb.com>

Al, could you please apply this series for v4.7? I first sent it out
during the v4.5 cycle, it'd be great to be done with it, especially
since it's fixing a regression.

Here's the cover letter from v1:
http://www.spinics.net/lists/linux-fsdevel/msg94735.html

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                                | 5 +----
 4 files changed, 6 insertions(+), 8 deletions(-)

-- 
2.8.2

             reply	other threads:[~2016-05-11 22:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-11 22:16 Omar Sandoval [this message]
2016-05-11 22:16 ` [PATCH RESEND v3 1/2] coredump: get rid of coredump_params->written Omar Sandoval
2016-05-11 22:16 ` [PATCH RESEND v3 2/2] coredump: only charge written data against RLIMIT_CORE Omar Sandoval
2016-05-11 22:18 ` [PATCH RESEND v3 0/2] fix RLIMIT_CORE accounting for sparse dumps Al Viro

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=cover.1463004510.git.osandov@fb.com \
    --to=osandov@osandov.com \
    --cc=kernel-team@fb.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=osandov@fb.com \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox