From: Kees Cook <keescook@chromium.org>
To: ebiederm@xmission.com
Cc: Kees Cook <keescook@chromium.org>,
linux-arm-kernel@lists.infradead.org, dalias@libc.org,
aou@eecs.berkeley.edu, gerg@linux-m68k.org, geert@linux-m68k.org,
vapier@gentoo.org, palmer@dabbelt.com,
damien.lemoal@opensource.wdc.com,
linux-m68k@lists.linux-m68k.org, linux-riscv@lists.infradead.org,
Al Viro <viro@zeniv.linux.org.uk>,
stable@vger.kernel.org, linux-fsdevel@vger.kernel.org,
paul.walmsley@sifive.com, ysato@users.sourceforge.jp,
Niklas.Cassel@wdc.com, linux-sh@vger.kernel.org,
linux-mm@kvack.org, linux-arch@vger.kernel.org
Subject: Re: (subset) [PATCH] binfmt_flat: Remove shared library support
Date: Wed, 20 Apr 2022 17:05:47 -0700 [thread overview]
Message-ID: <165049954506.2420506.9909431091128831748.b4-ty@chromium.org> (raw)
In-Reply-To: <87levzzts4.fsf_-_@email.froward.int.ebiederm.org>
On Wed, 20 Apr 2022 09:58:03 -0500, Eric W. Biederman wrote:
> In a recent discussion[1] it was reported that the binfmt_flat library
> support was only ever used on m68k and even on m68k has not been used
> in a very long time.
>
> The structure of binfmt_flat is different from all of the other binfmt
> implementations becasue of this shared library support and it made
> life and code review more effort when I refactored the code in fs/exec.c.
>
> [...]
It seems like there is agreement that the shared library support is
unused, so let's test that assumption. :)
With typos fixed up, applied to for-next/execve, thanks!
[1/1] binfmt_flat: Remove shared library support
https://git.kernel.org/kees/c/c85b5d88951b
--
Kees Cook
next prev parent reply other threads:[~2022-04-21 0:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 9:10 [PATCH v2] binfmt_flat: do not stop relocating GOT entries prematurely on riscv Niklas Cassel
2022-04-14 23:05 ` Kees Cook
2022-04-15 1:24 ` Niklas Cassel
2022-04-14 23:27 ` Kees Cook
2022-04-14 23:41 ` Damien Le Moal
2022-04-15 1:26 ` Konstantin Ryabitsev
2022-04-16 0:14 ` Kees Cook
2022-04-14 23:51 ` Damien Le Moal
2022-04-15 0:30 ` Niklas Cassel
2022-04-15 0:56 ` Damien Le Moal
2022-04-15 1:08 ` Niklas Cassel
2022-04-15 1:13 ` Damien Le Moal
2022-04-15 2:11 ` Niklas Cassel
2022-04-15 2:14 ` Damien Le Moal
2022-04-20 4:04 ` Greg Ungerer
2022-04-20 14:58 ` [PATCH] binfmt_flat: Remove shared library support Eric W. Biederman
2022-04-20 16:17 ` Palmer Dabbelt
2022-04-20 16:59 ` Rich Felker
2022-04-20 17:47 ` Kees Cook
2022-04-20 20:04 ` Arnd Bergmann
2022-04-20 20:23 ` Rich Felker
2022-04-20 23:00 ` Damien Le Moal
2022-04-25 3:38 ` Rob Landley
2022-04-25 7:40 ` Greg Ungerer
2022-04-20 23:36 ` Damien Le Moal
2022-04-20 23:53 ` Greg Ungerer
2022-04-21 6:52 ` Geert Uytterhoeven
2022-04-21 7:12 ` Arnd Bergmann
2022-04-22 10:26 ` Vladimir Murzin
2022-04-22 15:18 ` Patrice CHOTARD
2022-04-21 12:43 ` Rich Felker
2022-04-25 3:50 ` Rob Landley
2022-04-21 0:05 ` Kees Cook [this message]
2022-04-16 4:25 ` [PATCH v2] binfmt_flat: do not stop relocating GOT entries prematurely on riscv Kees Cook
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=165049954506.2420506.9909431091128831748.b4-ty@chromium.org \
--to=keescook@chromium.org \
--cc=Niklas.Cassel@wdc.com \
--cc=aou@eecs.berkeley.edu \
--cc=dalias@libc.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=ebiederm@xmission.com \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=stable@vger.kernel.org \
--cc=vapier@gentoo.org \
--cc=viro@zeniv.linux.org.uk \
--cc=ysato@users.sourceforge.jp \
/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