Received: by 10.213.65.68 with SMTP id h4csp1558786imn; Thu, 15 Mar 2018 03:15:01 -0700 (PDT) X-Google-Smtp-Source: AG47ELvhWt9mDecIKFvNc97JiOOQzJRKQ4ENhcnDVJTksR2SHSdVm9cGwnazJYKNqSKeJbrcSbrz X-Received: by 2002:a17:902:2884:: with SMTP id f4-v6mr3944240plb.153.1521108901611; Thu, 15 Mar 2018 03:15:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521108901; cv=none; d=google.com; s=arc-20160816; b=hPxp8bk7Lx4J9rqt1qHOb97sz2vgBGK+ICjYNZFdjGlY7sG6fAWMDrSiwIW8589hw1 LsX/4j7ezzZqTT5rydRyTOesKgoo93uPV64JnoI14a+NWdJrPeK2By4HkwHksoFggKFJ P+bL/mlEwZ7W/PvUY3NXLDgWO8XBi0bvU4hL4fK0niBpA1BRHrCHTO5Zli9QePj8xEoF z4EIrNTOLG2n+V8K/38+eHyBpv1gi+P0ex8EqB9M3AXsnpUYjzvY5WWEMvtp6qp0P4gJ DvQk2jgQlmR2YQtg29QKDVlKGQ6JfAP0uGIW0iBx0qtZI7tCtsUSiPIi2DeJnYw6iv4f I/bg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-transfer-encoding :mime-version:organization:references:in-reply-to:subject:cc:to:from :date:arc-authentication-results; bh=hh8OE1EENP+cpAQciw3DWZH4lP7ZcBC1FMeRcKOCChI=; b=XOwGlIZVnfsdGNnMFJ/QWQXWMysMw5knAZ4Mr8ZR37Ki+pMsoh8vwuqmp0VFfPe5Ml e255c2m3CJ++omzZ3n9XXpMTgW7xkcTe4oVMME/9LS55bxXm6ICqJGFoUa2OMqu+n57U OAiEAndMo82AjjgJ6oxSRdlMrhSOWBlQpx5qjUdL/X8GrZg6bHcQW/ggsxF9SVbjLvf+ 6AT5RNklLnnS2k+EuG5I93G2zKmuoiVfwvkL2wr57/UnNPzLne63K0xaEzORn7aLuybl uc4x+X8xhNL/gx7sQgYXm7TGkL3WunfPGobjhMQ5MC8YIw8073t3XuEkpnKIFYgl69wF vPLw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z16-v6si1891830pll.36.2018.03.15.03.14.47; Thu, 15 Mar 2018 03:15:01 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751597AbeCOKNy (ORCPT + 99 others); Thu, 15 Mar 2018 06:13:54 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:48060 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750745AbeCOKNw (ORCPT ); Thu, 15 Mar 2018 06:13:52 -0400 Received: from pps.filterd (m0098410.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w2FA9kHu147329 for ; Thu, 15 Mar 2018 06:13:51 -0400 Received: from e06smtp14.uk.ibm.com (e06smtp14.uk.ibm.com [195.75.94.110]) by mx0a-001b2d01.pphosted.com with ESMTP id 2gqmj3xw9e-1 (version=TLSv1.2 cipher=AES256-SHA256 bits=256 verify=NOT) for ; Thu, 15 Mar 2018 06:13:51 -0400 Received: from localhost by e06smtp14.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 15 Mar 2018 10:13:49 -0000 Received: from b06cxnps4076.portsmouth.uk.ibm.com (9.149.109.198) by e06smtp14.uk.ibm.com (192.168.101.144) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Thu, 15 Mar 2018 10:13:43 -0000 Received: from d06av26.portsmouth.uk.ibm.com (d06av26.portsmouth.uk.ibm.com [9.149.105.62]) by b06cxnps4076.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id w2FADhjW57278630; Thu, 15 Mar 2018 10:13:43 GMT Received: from d06av26.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 422E9AE045; Thu, 15 Mar 2018 10:04:09 +0000 (GMT) Received: from d06av26.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id B47DBAE051; Thu, 15 Mar 2018 10:04:08 +0000 (GMT) Received: from ThinkPad (unknown [9.152.212.63]) by d06av26.portsmouth.uk.ibm.com (Postfix) with ESMTP; Thu, 15 Mar 2018 10:04:08 +0000 (GMT) Date: Thu, 15 Mar 2018 11:13:41 +0100 From: Philipp Rudo To: Dave Young Cc: linux-s390@vger.kernel.org, Heiko Carstens , AKASHI Takahiro , Michael Ellerman , x86@kernel.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, Martin Schwidefsky , Eric Biederman , Thiago Jung Bauermann , Andrew Morton , Vivek Goyal , Ingo Molnar Subject: Re: [PATCH 00/11] kexec_file: Clean up purgatory load In-Reply-To: <20180315073422.GA1876@dhcp-128-65.nay.redhat.com> References: <20180226151620.20970-1-prudo@linux.vnet.ibm.com> <20180309051913.GA9358@dhcp-128-65.nay.redhat.com> <20180309152556.0ccf3cb1@ThinkPad> <20180312074016.GA1854@dhcp-128-65.nay.redhat.com> <20180315073422.GA1876@dhcp-128-65.nay.redhat.com> Organization: IBM X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 x-cbid: 18031510-0016-0000-0000-000005330357 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18031510-0017-0000-0000-000028700C6C Message-Id: <20180315111341.6faa90e8@ThinkPad> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-03-15_05:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1803150116 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Dave, On Thu, 15 Mar 2018 15:34:22 +0800 Dave Young wrote: > On 03/12/18 at 03:40pm, Dave Young wrote: > > Hi Philipp, > > On 03/09/18 at 03:25pm, Philipp Rudo wrote: > > > Hi Dave, > > > > > > On Fri, 9 Mar 2018 13:19:40 +0800 > > > Dave Young wrote: > > > > > > > Hi Philipp, > > > > On 02/26/18 at 04:16pm, Philipp Rudo wrote: > > > > > > > > > > Hi everybody > > > > > > > > > > following the discussion with Dave and AKASHI, here are the common code > > > > > patches extracted from my recent patch set (Add kexec_file_load support to > > > > > s390) [1]. The patches were extracted to allow upstream integration together > > > > > with AKASHI's common code patches before the arch code gets adjusted to the > > > > > new base. > > > > > > > > > > The reason for this series is to prepare common code for adding > > > > > kexec_file_load to s390 as well as cleaning up the mis-use of the sh_offset > > > > > field during purgatory load. In detail this series contains: > > > > > > > > > > Patch #1&2: Minor cleanups/fixes. > > > > > > > > > > Patch #3-9: Clean up the purgatory load/relocation code. Especially remove > > > > > the mis-use of the purgatory_info->sechdrs->sh_offset field, currently > > > > > holding a pointer into either kexec_purgatory (ro) or purgatory_buf (rw) > > > > > depending on the section. With these patches the section address will be > > > > > calculated verbosely and sh_offset will contain the offset of the section > > > > > in the stripped purgatory binary (purgatory_buf). > > > > > > > > > > Patch #10: Allows architectures to set the purgatory load address. This > > > > > patch is important for s390 as the kernel and purgatory have to be loaded > > > > > to fixed addresses. In current code this is impossible as the purgatory > > > > > load is opaque to the architecture. > > > > > > > > > > Patch #11: Moves x86 purgatories sha implementation to common lib/ > > > > > directory to allow reuse in other architectures. > > > > > > > > > > The patches apply to v4.16-rc3. There are no changes compared to [1] (all > > > > > requested changes only affected s390 code). Please note that I had to touch > > > > > arch code for x86 and power a little. In theory this should not change the > > > > > behavior but I don't have a way to test it. Cross-compiling with > > > > > defconfig [2] works fine for both. > > > > > > > > > > Thanks > > > > > Philipp > > > > > > > > > > [1] http://lists.infradead.org/pipermail/kexec/2018-February/019926.html > > > > > [2] On x86 with the orc unwinder and stack validation turned off. objtool > > > > > SEGFAULTs on s390... > > > > > > > > > > Philipp Rudo (11): > > > > > kexec_file: Silence compile warnings > > > > > kexec_file: Remove checks in kexec_purgatory_load > > > > > kexec_file: Make purgatory_info->ehdr const > > > > > kexec_file: Search symbols in read-only kexec_purgatory > > > > > kexec_file: Use read-only sections in arch_kexec_apply_relocations* > > > > > kexec_file: Split up __kexec_load_puragory > > > > > kexec_file: Simplify kexec_purgatory_setup_sechdrs 1 > > > > > kexec_file: Simplify kexec_purgatory_setup_sechdrs 2 > > > > > kexec_file: Remove mis-use of sh_offset field > > > > > kexec_file: Allow archs to set purgatory load address > > > > > kexec_file: Move purgatories sha256 to common code > > > > > > > > > > arch/powerpc/kernel/kexec_elf_64.c | 9 +- > > > > > arch/x86/kernel/kexec-bzimage64.c | 8 +- > > > > > arch/x86/kernel/machine_kexec_64.c | 66 ++--- > > > > > arch/x86/purgatory/Makefile | 3 + > > > > > arch/x86/purgatory/purgatory.c | 2 +- > > > > > include/linux/kexec.h | 38 +-- > > > > > {arch/x86/purgatory => include/linux}/sha256.h | 10 +- > > > > > kernel/kexec_file.c | 375 ++++++++++++------------- > > > > > {arch/x86/purgatory => lib}/sha256.c | 4 +- > > > > > 9 files changed, 244 insertions(+), 271 deletions(-) > > > > > rename {arch/x86/purgatory => include/linux}/sha256.h (63%) > > > > > rename {arch/x86/purgatory => lib}/sha256.c (99%) > > > > > > > > > > -- > > > > > 2.13.5 > > > > > > > > > > > > > I did a test on x86, but it failed: > > > > [ 15.636489] kexec: Undefined symbol: memcpy > > > > [ 15.636496] kexec-bzImage64: Loading purgatory failed > > > > [ 33.603356] kexec: Undefined symbol: memcpy > > > > [ 33.603362] kexec-bzImage64: Loading purgatory failed > > > > > > > > I think this relates to the sha256 splitting patch. > > > > > > I looked into this a little closer and i think i understood what happens. > > > > > > There is no definition of memcpy in arch/x86/boot/string.c, instead it's defined > > > in arch/x86/boot/string.h as __buildin_memcpy (same for memset). Thus by > > > switching to linux/string.h there is no more definition for it. Leaving us with > > > > > > $ readelf -s purgatory.ro > > > [...] > > > 45: 0000000000000000 0 NOTYPE GLOBAL DEFAULT UND memcpy > > > [...] > > > > > > To solve this problem I see two possibilities (example patches are at the end of > > > the mail): > > > > > > 1) Have arch dependent includes in lib/sha256.c > > > 2) Add makefile magic so memcpy is defined > > > > > > With both solutions the resulting purgatory.ro looks good. However both > > > solutions aren't perfect. For example in 2) i had too mix the linux/string.h > > > header with arch/x86/boot/string.c, because lib/string.c has too many > > > dependencies and does not compile in the purgatory. On the other hand having > > > arch dependent includes isn't that nice either ... > > > > > > What's your opinion on this? > > > > Looks like it is a mess, maybe the 1st one is better although it is also > > ugly. Ccing Ingo see if he has some idea about this. > > Maybe something like below is better if no other idea: > > diff --git a/arch/x86/boot/string_builtin.c b/arch/x86/boot/string_builtin.c > new file mode 100644 > index 000000000000..9099f949fb41 > --- /dev/null > +++ b/arch/x86/boot/string_builtin.c > @@ -0,0 +1,11 @@ > +#include > + > +void *memcpy(void *dst, const void *src, size_t len) > +{ > + return __builtin_memcpy(dst, src, len); > +} > + > +void *memset(void *dst, int c, size_t len) > +{ > + return __builtin_memset(dst, c, len); > +} > diff --git a/arch/x86/purgatory/string.c b/arch/x86/purgatory/string.c > index d886b1fa36f0..e12c78fcd59f 100644 > --- a/arch/x86/purgatory/string.c > +++ b/arch/x86/purgatory/string.c > @@ -11,3 +11,4 @@ > */ > > #include "../boot/string.c" > +#include "../boot/string_builtin.c" Looks like a good idea to me. Just to be sure, with this suggestion lib/sha256.c stays unchanged, i.e. it includes linux/string.h? The only thing I don't really like is adding the extra boot/string.builtin.c file. For my taste adding the two functions directly to purgatory/string.c would be nicer. However in the end it's "not my problem". Thanks Philipp > > > > > > > > Thanks > > > Philipp > > > > > > ----- > > > Example solution 1 > > > > > > --- a/lib/sha256.c > > > +++ b/lib/sha256.c > > > @@ -17,9 +17,14 @@ > > > > > > #include > > > #include > > > -#include > > > #include > > > > > > +#ifdef CONFIG_X86 > > > +#include "../arch/x86/boot/string.h" > > > +#else > > > +#include > > > +#endif /* CONFIG_X86 */ > > > + > > > static inline u32 Ch(u32 x, u32 y, u32 z) > > > { > > > return z ^ (x & (y ^ z)); > > > > > > ----- > > > Example solution 2 > > > > > > --- a/arch/x86/purgatory/Makefile > > > +++ b/arch/x86/purgatory/Makefile > > > @@ -1,7 +1,8 @@ > > > # SPDX-License-Identifier: GPL-2.0 > > > OBJECT_FILES_NON_STANDARD := y > > > > > > -purgatory-y := purgatory.o stack.o setup-x86_$(BITS).o sha256.o entry64.o string.o > > > +purgatory-y := purgatory.o stack.o setup-x86_$(BITS).o sha256.o entry64.o \ > > > + string.o memcpy_$(BITS).o memset_$(BITS).o > > > > > > targets += $(purgatory-y) > > > PURGATORY_OBJS = $(addprefix $(obj)/,$(purgatory-y)) > > > @@ -9,6 +10,15 @@ PURGATORY_OBJS = $(addprefix $(obj)/,$(purgatory-y)) > > > $(obj)/sha256.o: $(srctree)/lib/sha256.c > > > $(call if_changed_rule,cc_o_c) > > > > > > +$(obj)/string.o: $(srctree)/arch/x86/boot/string.c > > > + $(call if_changed_rule,cc_o_c) > > > + > > > +$(obj)/memset_$(BITS).o: $(srctree)/arch/x86/lib/memset_$(BITS).S > > > + $(call if_changed_rule,as_o_S) > > > + > > > +$(obj)/memcpy_$(BITS).o: $(srctree)/arch/x86/lib/memcpy_$(BITS).S > > > + $(call if_changed_rule,as_o_S) > > > + > > > LDFLAGS_purgatory.ro := -e purgatory_start -r --no-undefined -nostdlib -z nodefaultlib > > > targets += purgatory.ro > > > > > > > > > > Thanks > > Dave >