Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Kees Cook <keescook@chromium.org>
To:     ebiederm@xmission.com
Cc:     Kees Cook <keescook@chromium.org>, linux-kernel@vger.kernel.org,
        linux-arch@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [PATCH] a.out: Remove the a.out implementation
Date:   Mon, 26 Sep 2022 19:36:33 -0700
Message-Id: <166424619048.1957636.14312901276184216710.b4-ty@chromium.org>
In-Reply-To: <871qrx3hq3.fsf@email.froward.int.ebiederm.org>
References: <871qrx3hq3.fsf@email.froward.int.ebiederm.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Mon, 26 Sep 2022 17:15:32 -0500, Eric W. Biederman wrote:
> In commit 19e8b701e258 ("a.out: Stop building a.out/osf1 support on
> alpha and m68k") the last users of a.out were disabled.
> 
> As nothing has turned up to cause this change to be reverted, let's
> remove the code implementing a.out support as well.
> 
> There may be userspace users of the uapi bits left so the uapi
> headers have been left untouched.
> 
> [...]

Let's do it! It can always be reverted. :) My favorite kind of patch:

>  22 files changed, 1 insertion(+), 505 deletions(-)
                                     ^^^^^^^^^^^^^^

Applied to for-next/execve, thanks!

[1/1] a.out: Remove the a.out implementation
      https://git.kernel.org/kees/c/795d91fe0e13

-- 
Kees Cook