From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 87568C433ED for ; Tue, 18 May 2021 16:02:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 70CC761028 for ; Tue, 18 May 2021 16:02:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1350232AbhERQDj (ORCPT ); Tue, 18 May 2021 12:03:39 -0400 Received: from out02.mta.xmission.com ([166.70.13.232]:41974 "EHLO out02.mta.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344303AbhERQDe (ORCPT ); Tue, 18 May 2021 12:03:34 -0400 Received: from in01.mta.xmission.com ([166.70.13.51]) by out02.mta.xmission.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1lj2Ac-00AUYJ-9D; Tue, 18 May 2021 10:02:10 -0600 Received: from ip68-227-160-95.om.om.cox.net ([68.227.160.95] helo=fess.xmission.com) by in01.mta.xmission.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.87) (envelope-from ) id 1lj2AZ-0004Ye-GI; Tue, 18 May 2021 10:02:10 -0600 From: ebiederm@xmission.com (Eric W. Biederman) To: Arnd Bergmann Cc: linux-arch , Christoph Hellwig , Alexander Viro , Andrew Morton , Borislav Petkov , Brian Gerst , Ingo Molnar , "H. Peter Anvin" , Thomas Gleixner , Linux ARM , Linux Kernel Mailing List , Linux-MM , kexec@lists.infradead.org References: <20210517203343.3941777-1-arnd@kernel.org> <20210517203343.3941777-2-arnd@kernel.org> Date: Tue, 18 May 2021 11:01:57 -0500 In-Reply-To: (Arnd Bergmann's message of "Tue, 18 May 2021 16:17:53 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-XM-SPF: eid=1lj2AZ-0004Ye-GI;;;mid=;;;hst=in01.mta.xmission.com;;;ip=68.227.160.95;;;frm=ebiederm@xmission.com;;;spf=neutral X-XM-AID: U2FsdGVkX1/3KUt9n9NsCywLTywTeK8LOKWYroFccQo= X-SA-Exim-Connect-IP: 68.227.160.95 X-SA-Exim-Mail-From: ebiederm@xmission.com Subject: Re: [PATCH v3 1/4] kexec: simplify compat_sys_kexec_load X-SA-Exim-Version: 4.2.1 (built Thu, 05 May 2016 13:38:54 -0600) X-SA-Exim-Scanned: Yes (on in01.mta.xmission.com) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Arnd Bergmann writes: > On Tue, May 18, 2021 at 4:05 PM Arnd Bergmann wrote: >> >> On Tue, May 18, 2021 at 3:41 PM Eric W. Biederman wrote: >> > >> > Arnd Bergmann writes: >> > >> > > From: Arnd Bergmann KEXEC_ARCH_DEFAULT >> > > >> > > The compat version of sys_kexec_load() uses compat_alloc_user_space to >> > > convert the user-provided arguments into the native format. >> > > >> > > Move the conversion into the regular implementation with >> > > an in_compat_syscall() check to simplify it and avoid the >> > > compat_alloc_user_space() call. >> > > >> > > compat_sys_kexec_load() now behaves the same as sys_kexec_load(). >> > >> > Nacked-by: "Eric W. Biederman" >> >KEXEC_ARCH_DEFAULT >> > The patch is wrong. >> > >> > The logic between the compat entry point and the ordinary entry point >> > are by necessity different. This unifies the logic and breaks the compat >> > entry point. >> > >> > The fundamentally necessity is that the code being loaded needs to know >> > which mode the kernel is running in so it can safely transition to the >> > new kernel. >> > >> > Given that the two entry points fundamentally need different logic, >> > and that difference was not preserved and the goal of this patchset >> > was to unify that which fundamentally needs to be different. I don't >> > think this patch series makes any sense for kexec. >> >> Sorry, I'm not following that explanation. Can you clarify what different >> modes of the kernel you are referring to here, and how my patch >> changes this? > > I think I figured it out now myself after comparing the two functions: > > --- a/kernel/kexec.c > +++ b/kernel/kexec.c > @@ -269,7 +269,8 @@ SYSCALL_DEFINE4(kexec_load, unsigned long, entry, > unsigned long, nr_segments, > > /* Verify we are on the appropriate architecture */ > if (((flags & KEXEC_ARCH_MASK) != KEXEC_ARCH) && > - ((flags & KEXEC_ARCH_MASK) != KEXEC_ARCH_DEFAULT)) > + (in_compat_syscall() || > + ((flags & KEXEC_ARCH_MASK) != KEXEC_ARCH_DEFAULT))) > return -EINVAL; > > /* Because we write directly to the reserved memory > > Not sure if that's the best way of doing it, but it looks like folding this > in restores the current behavior. Yes. That is pretty much all there is. I personally can't stand the sight of in_compat_syscall() doubly so when you have to lie to the type system with casts. The cognitive dissonance I experience is extreme. I will be happy to help you find another way to get rid of compat_alloc_user, but not that way. There is a whole mess in there that was introduced when someone added do_kexec_load while I was napping in 2017 that makes the system calls an absolute mess. It all needs to be cleaned up. Eric