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=-15.2 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, USER_AGENT_SANE_1 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 70085C433E0 for ; Tue, 23 Feb 2021 00:42:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2F33B64E4D for ; Tue, 23 Feb 2021 00:42:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231313AbhBWAmT (ORCPT ); Mon, 22 Feb 2021 19:42:19 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49586 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230511AbhBWAmK (ORCPT ); Mon, 22 Feb 2021 19:42:10 -0500 Received: from mail-pj1-x1029.google.com (mail-pj1-x1029.google.com [IPv6:2607:f8b0:4864:20::1029]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 49FE8C06174A for ; Mon, 22 Feb 2021 16:41:30 -0800 (PST) Received: by mail-pj1-x1029.google.com with SMTP id cx11so700477pjb.4 for ; Mon, 22 Feb 2021 16:41:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20150623.gappssmtp.com; s=20150623; h=subject:from:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=075DZHDc92upqmRp6tbGPpItl5hmgDvrCYmFEEi/OOU=; b=10UAv5jul/fxr9I89Yb62NhtAJux1zMNuqNSQteVV+uuOXQ69tU3lNhmHioG4ksllG zw/fcSdnKlqueXmMBfKI7IbJ47DenyBB6E6YACIjfLZLv0BqpFk+OpnfOORQuYgV9830 sUCOSN6A6X6BhAG6EeSKwlPOxMPDONajslM0Jn2rJMNkhzUeY/2cbgYjg4zngtYbj79S tUfHIyX9Y6yeMOjfKXzvzpcjf4hA/LkteTkBcdiozR0Wh6FjU06gBz0ydSH+dSsqnD+G Ydme1gaew557iGoodfmbHaX0It1Y78agqRaoiGAYyQ8+SwX6X3YlKHHyH5Qjm5f8/x4/ FA/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=075DZHDc92upqmRp6tbGPpItl5hmgDvrCYmFEEi/OOU=; b=qDvwtuW/4m8s2YSGQbbupmCF42OM+sXBsTtAKeU+RbZYH3UirSoQrEuAs3l0gfGdU0 VIW6Yf4VmqtHhlVFCkdFXUuPZkAtPYo/mO9SZAZrSHijodwlCmk/sXLZ8f66I2R9Bw0W QLaZ0cInKS7fpXTvo320qGKKptDyo6aRUl4e/j8lT4tLZUgF3aHrIy2UoBqvB4ML89Bz aPXI3q+WBnKzjMh0bmplGAGGI694OeSwKr6oCExRkiCWSEGjDru1hRxhmDT+0+rAEr6+ 49b5px+yr7YUrfAPkCsNmpBf8UejbZmXc1Y4iPzpDzMvfXr9vhIRebYoQ7cttKPGmAYk vv6w== X-Gm-Message-State: AOAM5338CyAwMGqaMIoz/B0GuFPHn77yKIpELTuY+8LRGz7P7OEzOpLJ 58xX2oGz2BJ00ATOEIrr8ap+9K2ezkOcAPYb X-Google-Smtp-Source: ABdhPJwhnnZu9jMjXm/JUnEGI4kLyIOyZHJAW5uwibOv8FYpmOQZ5zPBdw0rQ9LrHoxI86o+2J7sTw== X-Received: by 2002:a17:90a:4603:: with SMTP id w3mr26783800pjg.125.1614040889314; Mon, 22 Feb 2021 16:41:29 -0800 (PST) Received: from ?IPv6:2600:380:497c:8b1b:6d68:602d:6c32:8715? ([2600:380:497c:8b1b:6d68:602d:6c32:8715]) by smtp.gmail.com with ESMTPSA id u14sm679245pjf.15.2021.02.22.16.41.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 22 Feb 2021 16:41:28 -0800 (PST) Subject: Re: 5.11 regression: "ia64: add support for TIF_NOTIFY_SIGNAL" breaks ia64 boot From: Jens Axboe To: Sergei Trofimovich Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org References: <20210222230519.73f3e239@sf> <20210222235359.75d1a912@sf> Message-ID: <30a833d8-44a0-284d-4fe4-e9a52f407043@kernel.dk> Date: Mon, 22 Feb 2021 17:41:27 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/22/21 5:34 PM, Jens Axboe wrote: > On 2/22/21 4:53 PM, Sergei Trofimovich wrote: >> On Mon, 22 Feb 2021 16:34:50 -0700 >> Jens Axboe wrote: >> >>> On 2/22/21 4:05 PM, Sergei Trofimovich wrote: >>>> Hia Jens! >>>> >>>> Tried 5.11 on rx3600 box and noticed it has >>>> a problem handling init (5.10 booted fine): >>>> >>>> INIT: version 2.98 booting >>>> >>>> OpenRC 0.42.1 is starting up Gentoo Linux (ia64) >>>> >>>> mkdir `/run/openrc': Read-only file system >>>> mkdir `/run/openrc/starting': No such file or directory >>>> mkdir `/run/openrc/started': No such file or directory >>>> mkdir `/run/openrc/stopping': No such file or directory >>>> mkdir `/run/openrc/inactive': No such file or directory >>>> mkdir `/run/openrc/wasinactive': No such file or directory >>>> mkdir `/run/openrc/failed': No such file or directory >>>> mkdir `/run/openrc/hotplugged': No such file or directory >>>> mkdir `/run/openrc/daemons': No such file or directory >>>> mkdir `/run[ 14.595059] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b >>>> [ 14.599059] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]--- >>>> >>>> I suspect we build bad signal stack frame for userspace. >>>> >>>> With a bit of #define DEBUG_SIG 1 enabled the signals are SIGCHLD: >>>> >>>> [ 34.969771] SIG deliver (gendepends.sh:69): sig=17 sp=60000fffff6aeaa0 ip=a000000000040740 handler=000000004b4c59b6 >>>> [ 34.969948] SIG deliver (init:1): sig=17 sp=60000fffff1ccc50 ip=a000000000040740 handler=000000004638b9e5 >>>> [ 34.969948] SIG deliver (gendepends.sh:69): sig=17 sp=60000fffff6adf90 ip=a000000000040740 handler=000000004b4c59b6 >>>> [ 34.973948] SIG deliver (init:1): sig=17 sp=60000fffff1cc140 ip=a000000000040740 handler=000000004638b9e5 >>>> [ 34.973948] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b >>>> [ 34.973948] SIG deliver (gendepends.sh:69): sig=17 sp=60000fffff6ad480 ip=a000000000040740 handler=000000004b4c59b6 >>>> [ 34.973948] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]--- >>>> >>>> Bisect points at: >>>> >>>> commit b269c229b0e89aedb7943c06673b56b6052cf5e5 >>>> Author: Jens Axboe >>>> Date: Fri Oct 9 14:49:43 2020 -0600 >>>> >>>> ia64: add support for TIF_NOTIFY_SIGNAL >>>> >>>> Wire up TIF_NOTIFY_SIGNAL handling for ia64. >>>> >>>> Cc: linux-ia64@vger.kernel.org >>>> [axboe: added fixes from Mike Rapoport ] >>>> Signed-off-by: Jens Axboe >>>> >>>> diff --git a/arch/ia64/include/asm/thread_info.h b/arch/ia64/include/asm/thread_info.h >>>> index 64a1011f6812..51d20cb37706 100644 >>>> --- a/arch/ia64/include/asm/thread_info.h >>>> +++ b/arch/ia64/include/asm/thread_info.h >>>> @@ -103,6 +103,7 @@ struct thread_info { >>>> #define TIF_SYSCALL_TRACE 2 /* syscall trace active */ >>>> #define TIF_SYSCALL_AUDIT 3 /* syscall auditing active */ >>>> #define TIF_SINGLESTEP 4 /* restore singlestep on return to user mode */ >>>> +#define TIF_NOTIFY_SIGNAL 5 /* signal notification exist */ >>>> #define TIF_NOTIFY_RESUME 6 /* resumption notification requested */ >>>> #define TIF_MEMDIE 17 /* is terminating due to OOM killer */ >>>> #define TIF_MCA_INIT 18 /* this task is processing MCA or INIT */ >>>> @@ -115,6 +116,7 @@ struct thread_info { >>>> #define _TIF_SINGLESTEP (1 << TIF_SINGLESTEP) >>>> #define _TIF_SYSCALL_TRACEAUDIT (_TIF_SYSCALL_TRACE|_TIF_SYSCALL_AUDIT|_TIF_SINGLESTEP) >>>> #define _TIF_NOTIFY_RESUME (1 << TIF_NOTIFY_RESUME) >>>> +#define _TIF_NOTIFY_SIGNAL (1 << TIF_NOTIFY_SIGNAL) >>>> #define _TIF_SIGPENDING (1 << TIF_SIGPENDING) >>>> #define _TIF_NEED_RESCHED (1 << TIF_NEED_RESCHED) >>>> #define _TIF_MCA_INIT (1 << TIF_MCA_INIT) >>>> @@ -124,7 +126,7 @@ struct thread_info { >>>> >>>> /* "work to do on user-return" bits */ >>>> #define TIF_ALLWORK_MASK (_TIF_SIGPENDING|_TIF_NOTIFY_RESUME|_TIF_SYSCALL_AUDIT|\ >>>> - _TIF_NEED_RESCHED|_TIF_SYSCALL_TRACE) >>>> + _TIF_NEED_RESCHED|_TIF_SYSCALL_TRACE|_TIF_NOTIFY_SIGNAL) >>>> /* like TIF_ALLWORK_BITS but sans TIF_SYSCALL_TRACE or TIF_SYSCALL_AUDIT */ >>>> #define TIF_WORK_MASK (TIF_ALLWORK_MASK&~(_TIF_SYSCALL_TRACE|_TIF_SYSCALL_AUDIT)) >>>> >>>> diff --git a/arch/ia64/kernel/process.c b/arch/ia64/kernel/process.c >>>> index 6b61a703bcf5..8d4e1cab9190 100644 >>>> --- a/arch/ia64/kernel/process.c >>>> +++ b/arch/ia64/kernel/process.c >>>> @@ -171,7 +171,8 @@ do_notify_resume_user(sigset_t *unused, struct sigscratch *scr, long in_syscall) >>>> } >>>> >>>> /* deal with pending signal delivery */ >>>> - if (test_thread_flag(TIF_SIGPENDING)) { >>>> + if (test_thread_flag(TIF_SIGPENDING) || >>>> + test_thread_flag(TIF_NOTIFY_SIGNAL)) { >>>> local_irq_enable(); /* force interrupt enable */ >>>> ia64_do_signal(scr, in_syscall); >>>> >>>> which looks benign, but it enables a bit of conditional >>>> TIF_NOTIFY_SIGNAL handling I don't understand. >>>> >>>> Can you help me get what is the interaction between >>>> TIF_NOTIFY_SIGNAL and TIF_SIGPENDING for >>>> simple processes without io_uring use case? >>>> >>>> I wonder if it's ia64_do_signal()' generates a signal >>>> delivery when it should not. >>> >>> Can you test: >>> >>> https://marc.info/?l=linux-ia64&m=161187407609443&w=1 >>> >>> with the addition mentioned here: >> >> Not enough: >> >> mkdir `/run/openrc': Read-only file system >> mkdir `/run/openrc/starting': No such file or directory >> mkdir `/run/openrc/started': No such file or directory >> mkdir `/run/openrc/stopping': No such file or directory >> mkdir `/run/openrc/inactive': No such file or directory >> mkdir `/run/openrc/wasinactive': No such file or directory >> mkdir `/run/openrc/failed': No such file or directory >> mkdir `/run/openrc/hotplugged': No such file or directory >> mkdir `/run/openrc/daemons': No such file or directory >> [ 14.554357] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b >> [ 14.554357] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]--- >> mkdir `/run/openrc/options': No such file or directory >> mkdir `/run/openrc/exclusive': No such file or directory >> mkdir `/run/openrc/scheduled': No such file or directory >> mkdir `/run/openrc/tmp': No such file or directory >> >>> https://marc.info/?l=linux-ia64&m=161187470709706&w=1 >>> >>> if needed? >> >> Two patches above do fix the boot \o/ But have a lot of spam about >> 'signal 0' delivery to a bunch of processes: >> >> * Mounting /proc ... >> [ ok ] >> * Mounting /run ... >> * /run/openrc: creating directory >> * /run/lock: creating directory >> * /run/lock: correcting owner >> * Caching service dependencies ... >> [ ok ] >> * Mounting /sys ... >> [ ok ] >> * Mounting debug filesystem ... >> [ ok ] >> * Mounting efivarfs filesystem ... >> [ ok ] >> * sysfs: caught unknown signal 0 >> * openrc: caught unknown signal 0 >> * Mounting cgroup filesystem ... > > That's an improvement! Let me take a look at this tonight and see if I > can figure out what's going on. But yes, it's the ia64 signal delivery > being just different enough from the norm that it apparently triggers > some weirdness. Is this any better? diff --git a/arch/ia64/kernel/signal.c b/arch/ia64/kernel/signal.c index e67b22fc3c60..11891240aa5c 100644 --- a/arch/ia64/kernel/signal.c +++ b/arch/ia64/kernel/signal.c @@ -340,8 +340,10 @@ ia64_do_signal (struct sigscratch *scr, long in_syscall) * This only loops in the rare cases of handle_signal() failing, in which case we * need to push through a forced SIGSEGV. */ - while (1) { - get_signal(&ksig); + do { + ksig.sig = 0; + if (!get_signal(&ksig)) + break; /* * get_signal() may have run a debugger (via notify_parent()) @@ -358,9 +360,6 @@ ia64_do_signal (struct sigscratch *scr, long in_syscall) */ restart = 0; - if (ksig.sig <= 0) - break; - if (unlikely(restart)) { switch (errno) { case ERESTART_RESTARTBLOCK: @@ -387,7 +386,7 @@ ia64_do_signal (struct sigscratch *scr, long in_syscall) */ if (handle_signal(&ksig, scr)) return; - } + } while (ksig.sig > 0); /* Did we come from a system call? */ if (restart) { -- Jens Axboe From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jens Axboe Date: Tue, 23 Feb 2021 00:41:27 +0000 Subject: Re: 5.11 regression: "ia64: add support for TIF_NOTIFY_SIGNAL" breaks ia64 boot Message-Id: <30a833d8-44a0-284d-4fe4-e9a52f407043@kernel.dk> List-Id: References: <20210222230519.73f3e239@sf> <20210222235359.75d1a912@sf> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: Sergei Trofimovich Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org On 2/22/21 5:34 PM, Jens Axboe wrote: > On 2/22/21 4:53 PM, Sergei Trofimovich wrote: >> On Mon, 22 Feb 2021 16:34:50 -0700 >> Jens Axboe wrote: >> >>> On 2/22/21 4:05 PM, Sergei Trofimovich wrote: >>>> Hia Jens! >>>> >>>> Tried 5.11 on rx3600 box and noticed it has >>>> a problem handling init (5.10 booted fine): >>>> >>>> INIT: version 2.98 booting >>>> >>>> OpenRC 0.42.1 is starting up Gentoo Linux (ia64) >>>> >>>> mkdir `/run/openrc': Read-only file system >>>> mkdir `/run/openrc/starting': No such file or directory >>>> mkdir `/run/openrc/started': No such file or directory >>>> mkdir `/run/openrc/stopping': No such file or directory >>>> mkdir `/run/openrc/inactive': No such file or directory >>>> mkdir `/run/openrc/wasinactive': No such file or directory >>>> mkdir `/run/openrc/failed': No such file or directory >>>> mkdir `/run/openrc/hotplugged': No such file or directory >>>> mkdir `/run/openrc/daemons': No such file or directory >>>> mkdir `/run[ 14.595059] Kernel panic - not syncing: Attempted to kil= l init! exitcode=3D0x0000000b >>>> [ 14.599059] ---[ end Kernel panic - not syncing: Attempted to kill = init! exitcode=3D0x0000000b ]--- >>>> >>>> I suspect we build bad signal stack frame for userspace. >>>> >>>> With a bit of #define DEBUG_SIG 1 enabled the signals are SIGCHLD: >>>> >>>> [ 34.969771] SIG deliver (gendepends.sh:69): sig=17 sp`000fffff6aeaa= 0 ip=A000000000040740 handler=000000004b4c59b6 >>>> [ 34.969948] SIG deliver (init:1): sig=17 sp`000fffff1ccc50 ip=A0000= 00000040740 handler=000000004638b9e5 >>>> [ 34.969948] SIG deliver (gendepends.sh:69): sig=17 sp`000fffff6adf9= 0 ip=A000000000040740 handler=000000004b4c59b6 >>>> [ 34.973948] SIG deliver (init:1): sig=17 sp`000fffff1cc140 ip=A0000= 00000040740 handler=000000004638b9e5 >>>> [ 34.973948] Kernel panic - not syncing: Attempted to kill init! exi= tcode=3D0x0000000b >>>> [ 34.973948] SIG deliver (gendepends.sh:69): sig=17 sp`000fffff6ad48= 0 ip=A000000000040740 handler=000000004b4c59b6 >>>> [ 34.973948] ---[ end Kernel panic - not syncing: Attempted to kill = init! exitcode=3D0x0000000b ]--- >>>> >>>> Bisect points at: >>>> >>>> commit b269c229b0e89aedb7943c06673b56b6052cf5e5 >>>> Author: Jens Axboe >>>> Date: Fri Oct 9 14:49:43 2020 -0600 >>>> >>>> ia64: add support for TIF_NOTIFY_SIGNAL >>>> >>>> Wire up TIF_NOTIFY_SIGNAL handling for ia64. >>>> >>>> Cc: linux-ia64@vger.kernel.org >>>> [axboe: added fixes from Mike Rapoport ] >>>> Signed-off-by: Jens Axboe >>>> >>>> diff --git a/arch/ia64/include/asm/thread_info.h b/arch/ia64/include/a= sm/thread_info.h >>>> index 64a1011f6812..51d20cb37706 100644 >>>> --- a/arch/ia64/include/asm/thread_info.h >>>> +++ b/arch/ia64/include/asm/thread_info.h >>>> @@ -103,6 +103,7 @@ struct thread_info { >>>> #define TIF_SYSCALL_TRACE 2 /* syscall trace active */ >>>> #define TIF_SYSCALL_AUDIT 3 /* syscall auditing active */ >>>> #define TIF_SINGLESTEP 4 /* restore singlestep on retur= n to user mode */ >>>> +#define TIF_NOTIFY_SIGNAL 5 /* signal notification exist */ >>>> #define TIF_NOTIFY_RESUME 6 /* resumption notification req= uested */ >>>> #define TIF_MEMDIE 17 /* is terminating due to OOM k= iller */ >>>> #define TIF_MCA_INIT 18 /* this task is processing MCA= or INIT */ >>>> @@ -115,6 +116,7 @@ struct thread_info { >>>> #define _TIF_SINGLESTEP (1 << TIF_SINGLESTEP) >>>> #define _TIF_SYSCALL_TRACEAUDIT (_TIF_SYSCALL_TRACE|_TIF_SYSCA= LL_AUDIT|_TIF_SINGLESTEP) >>>> #define _TIF_NOTIFY_RESUME (1 << TIF_NOTIFY_RESUME) >>>> +#define _TIF_NOTIFY_SIGNAL (1 << TIF_NOTIFY_SIGNAL) >>>> #define _TIF_SIGPENDING (1 << TIF_SIGPENDING) >>>> #define _TIF_NEED_RESCHED (1 << TIF_NEED_RESCHED) >>>> #define _TIF_MCA_INIT (1 << TIF_MCA_INIT) >>>> @@ -124,7 +126,7 @@ struct thread_info { >>>> >>>> /* "work to do on user-return" bits */ >>>> #define TIF_ALLWORK_MASK (_TIF_SIGPENDING|_TIF_NOTIFY_RESUME|_T= IF_SYSCALL_AUDIT|\ >>>> - _TIF_NEED_RESCHED|_TIF_SYSCALL_TRACE) >>>> + _TIF_NEED_RESCHED|_TIF_SYSCALL_TRACE|= _TIF_NOTIFY_SIGNAL) >>>> /* like TIF_ALLWORK_BITS but sans TIF_SYSCALL_TRACE or TIF_SYSCALL_AU= DIT */ >>>> #define TIF_WORK_MASK (TIF_ALLWORK_MASK&~(_TIF_SYSCALL_TRACE= |_TIF_SYSCALL_AUDIT)) >>>> >>>> diff --git a/arch/ia64/kernel/process.c b/arch/ia64/kernel/process.c >>>> index 6b61a703bcf5..8d4e1cab9190 100644 >>>> --- a/arch/ia64/kernel/process.c >>>> +++ b/arch/ia64/kernel/process.c >>>> @@ -171,7 +171,8 @@ do_notify_resume_user(sigset_t *unused, struct sig= scratch *scr, long in_syscall) >>>> } >>>> >>>> /* deal with pending signal delivery */ >>>> - if (test_thread_flag(TIF_SIGPENDING)) { >>>> + if (test_thread_flag(TIF_SIGPENDING) || >>>> + test_thread_flag(TIF_NOTIFY_SIGNAL)) { >>>> local_irq_enable(); /* force interrupt enable */ >>>> ia64_do_signal(scr, in_syscall); >>>> >>>> which looks benign, but it enables a bit of conditional >>>> TIF_NOTIFY_SIGNAL handling I don't understand. >>>> >>>> Can you help me get what is the interaction between >>>> TIF_NOTIFY_SIGNAL and TIF_SIGPENDING for >>>> simple processes without io_uring use case? >>>> >>>> I wonder if it's ia64_do_signal()' generates a signal >>>> delivery when it should not. =20 >>> >>> Can you test: >>> >>> https://marc.info/?l=3Dlinux-ia64&m=161187407609443&w=3D1 >>> >>> with the addition mentioned here: >> >> Not enough: >> >> mkdir `/run/openrc': Read-only file system >> mkdir `/run/openrc/starting': No such file or directory >> mkdir `/run/openrc/started': No such file or directory >> mkdir `/run/openrc/stopping': No such file or directory >> mkdir `/run/openrc/inactive': No such file or directory >> mkdir `/run/openrc/wasinactive': No such file or directory >> mkdir `/run/openrc/failed': No such file or directory >> mkdir `/run/openrc/hotplugged': No such file or directory >> mkdir `/run/openrc/daemons': No such file or directory >> [ 14.554357] Kernel panic - not syncing: Attempted to kill init! exitc= ode=3D0x0000000b >> [ 14.554357] ---[ end Kernel panic - not syncing: Attempted to kill in= it! exitcode=3D0x0000000b ]--- >> mkdir `/run/openrc/options': No such file or directory >> mkdir `/run/openrc/exclusive': No such file or directory >> mkdir `/run/openrc/scheduled': No such file or directory >> mkdir `/run/openrc/tmp': No such file or directory >> >>> https://marc.info/?l=3Dlinux-ia64&m=161187470709706&w=3D1 >>> >>> if needed? >> >> Two patches above do fix the boot \o/ But have a lot of spam about >> 'signal 0' delivery to a bunch of processes: >> >> * Mounting /proc ... >> [ ok ] >> * Mounting /run ... >> * /run/openrc: creating directory >> * /run/lock: creating directory >> * /run/lock: correcting owner >> * Caching service dependencies ... >> [ ok ] >> * Mounting /sys ... >> [ ok ] >> * Mounting debug filesystem ... >> [ ok ] >> * Mounting efivarfs filesystem ... >> [ ok ] >> * sysfs: caught unknown signal 0 >> * openrc: caught unknown signal 0 >> * Mounting cgroup filesystem ... >=20 > That's an improvement! Let me take a look at this tonight and see if I > can figure out what's going on. But yes, it's the ia64 signal delivery > being just different enough from the norm that it apparently triggers > some weirdness. Is this any better? diff --git a/arch/ia64/kernel/signal.c b/arch/ia64/kernel/signal.c index e67b22fc3c60..11891240aa5c 100644 --- a/arch/ia64/kernel/signal.c +++ b/arch/ia64/kernel/signal.c @@ -340,8 +340,10 @@ ia64_do_signal (struct sigscratch *scr, long in_syscal= l) * This only loops in the rare cases of handle_signal() failing, in which= case we * need to push through a forced SIGSEGV. */ - while (1) { - get_signal(&ksig); + do { + ksig.sig =3D 0; + if (!get_signal(&ksig)) + break; =20 /* * get_signal() may have run a debugger (via notify_parent()) @@ -358,9 +360,6 @@ ia64_do_signal (struct sigscratch *scr, long in_syscall) */ restart =3D 0; =20 - if (ksig.sig <=3D 0) - break; - if (unlikely(restart)) { switch (errno) { case ERESTART_RESTARTBLOCK: @@ -387,7 +386,7 @@ ia64_do_signal (struct sigscratch *scr, long in_syscall) */ if (handle_signal(&ksig, scr)) return; - } + } while (ksig.sig > 0); =20 /* Did we come from a system call? */ if (restart) { --=20 Jens Axboe