linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: ebiederm@xmission.com
Cc: Kees Cook <keescook@chromium.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	damien.lemoal@opensource.wdc.com, linux-mm@kvack.org,
	linux-fsdevel@vger.kernel.org, Niklas.Cassel@wdc.com,
	lkp@intel.com, vapier@gentoo.org, gerg@linux-m68k.org,
	stable@vger.kernel.org
Subject: Re: (subset) [PATCH] binfmt_flat; Drop vestigates of coredump support
Date: Tue, 19 Apr 2022 10:46:40 -0700	[thread overview]
Message-ID: <165039039729.809958.17874221541968744613.b4-ty@chromium.org> (raw)
In-Reply-To: <87mtgh17li.fsf_-_@email.froward.int.ebiederm.org>

On Tue, 19 Apr 2022 09:16:41 -0500, Eric W. Biederman wrote:
> There is the briefest start of coredump support in binfmt_flat.  It is
> actually a pain to maintain as binfmt_flat is not built on most
> architectures so it is easy to overlook.
> 
> Since the support does not do anything remove it.
> 
> 
> [...]

Applied to for-next/execve, thanks! (With typo nits fixed.)

[1/1] binfmt_flat; Drop vestigates of coredump support
      https://git.kernel.org/kees/c/6e1a873cefd1

-- 
Kees Cook



  parent reply	other threads:[~2022-04-19 17:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18 20:09 [PATCH] binfmt_flat: fix sparse annotation ordering Niklas Cassel
2022-04-18 22:01 ` Kees Cook
2022-04-19 14:16   ` [PATCH] binfmt_flat; Drop vestigates of coredump support Eric W. Biederman
2022-04-19 16:35     ` Niklas Cassel
2022-04-19 17:46     ` Kees Cook [this message]
2022-04-20 13:48       ` (subset) " Eric W. Biederman
2022-04-19 23:08     ` Greg Ungerer

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=165039039729.809958.17874221541968744613.b4-ty@chromium.org \
    --to=keescook@chromium.org \
    --cc=Niklas.Cassel@wdc.com \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=ebiederm@xmission.com \
    --cc=gerg@linux-m68k.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=vapier@gentoo.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