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=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham 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 2ECC0C282C0 for ; Thu, 24 Jan 2019 01:01:40 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 6A00821872 for ; Thu, 24 Jan 2019 01:01:39 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6A00821872 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 43lP4K0wKHzDqDN for ; Thu, 24 Jan 2019 12:01:37 +1100 (AEDT) Received: from ozlabs.org (bilbo.ozlabs.org [203.11.71.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 43lP2L5vB5zDqDN for ; Thu, 24 Jan 2019 11:59:54 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPSA id 43lP2L2dh3z9s3l; Thu, 24 Jan 2019 11:59:54 +1100 (AEDT) From: Michael Ellerman To: Christophe Leroy , Benjamin Herrenschmidt , Paul Mackerras , Nicholas Piggin , Mike Rapoport Subject: Re: [PATCH v13 00/10] powerpc: Switch to CONFIG_THREAD_INFO_IN_TASK In-Reply-To: <07e60b5a-611c-9863-f300-68a4f9ad2efd@c-s.fr> References: <87zhrx2bf1.fsf@concordia.ellerman.id.au> <07e60b5a-611c-9863-f300-68a4f9ad2efd@c-s.fr> Date: Thu, 24 Jan 2019 11:59:51 +1100 Message-ID: <871s52yins.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" Christophe Leroy writes: > Le 19/01/2019 =C3=A0 11:23, Michael Ellerman a =C3=A9crit=C2=A0: >> Christophe Leroy writes: >>=20 >>> The purpose of this serie is to activate CONFIG_THREAD_INFO_IN_TASK whi= ch >>> moves the thread_info into task_struct. >>> >>> Moving thread_info into task_struct has the following advantages: >>> - It protects thread_info from corruption in the case of stack >>> overflows. >>> - Its address is harder to determine if stack addresses are >>> leaked, making a number of attacks more difficult. >>> >>> Changes since v12: >>> - Patch 1: Taken comment from Mike (re-introduced the 'panic' in case= memblock allocation fails in setup_64.c >>> - Patch 1: Added alloc_stack() function in setup_32.c to also panic i= n case of allocation failure. >>=20 >> Hi Christophe, >>=20 >> I can't get this series to boot on qemu mac99. I'm getting eg: >>=20 >> [ 0.981514] NFS: Registering the id_resolver key type >> [ 0.981752] Key type id_resolver registered >> [ 0.981868] Key type id_legacy registered >> [ 0.995711] Unrecoverable exception 0 at 0 (msr=3D0) >> [ 0.996091] Oops: Unrecoverable exception, sig: 6 [#1] >> [ 0.996314] BE PAGE_SIZE=3D4K MMU=3DHash PowerMac >> [ 0.996617] Modules linked in: >> [ 0.996869] CPU: 0 PID: 416 Comm: modprobe Not tainted 5.0.0-rc2-gcc-= 7.3.0-00043-g53f2de798792 #342 >> [ 0.997138] NIP: 00000000 LR: 00000000 CTR: 00000000 >> [ 0.997309] REGS: ef237f50 TRAP: 0000 Not tainted (5.0.0-rc2-gcc-7= .3.0-00043-g53f2de798792) >> [ 0.997508] MSR: 00000000 <> CR: 00000000 XER: 00000000 >> [ 0.997712] >> [ 0.997712] GPR00: 00000000 ef238000 00000000 00000000 00000000 00000= 000 00000000 00000000 >> [ 0.997712] GPR08: 00000000 00000000 00000000 00000000 00000000 00000= 000 c006477c ef13d8c0 >> [ 0.997712] GPR16: 00000000 00000000 00000000 00000000 00000000 00000= 000 00000000 00000000 >> [ 0.997712] GPR24: 00000000 00000000 00000000 00000000 00000000 00000= 000 00000000 00000000 >> [ 0.998671] NIP [00000000] (null) >> [ 0.998774] LR [00000000] (null) >> [ 0.998895] Call Trace: >> [ 0.999030] Instruction dump: >> [ 0.999320] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXX= XXXXX XXXXXXXX >> [ 0.999546] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX 60000000 XXXXXXXX XXX= XXXXX XXXXXXXX >> [ 1.000023] ---[ end trace 925ea3419844fe68 ]--- > > No such issue on my side. Do you have a ramdisk with anythink special or= =20 > a special config ? I see your kernel is modprobing something, know what=20 > it is ? It's just a debian installer image, nothing special AFAIK. > Especially, what is the amount of memory in your config ? On my side=20 > there is 128M: I have 1G. But today I can't reproduce the crash :/ So I guess it must have been something else in my config. cheers