From: Casey Schaufler <casey@schaufler-ca.com>
To: lkp@lists.01.org
Subject: Re: [LSM] Kernel panic - not syncing: No working init found.
Date: Tue, 11 Nov 2014 16:10:41 -0800 [thread overview]
Message-ID: <5462A581.4050101@schaufler-ca.com> (raw)
In-Reply-To: <CAGXu5jJdB6pq5WqHWSAaGRmRvgkrzoq95PjHTf7GtSkUGmEchA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3456 bytes --]
On 11/5/2014 10:15 AM, Kees Cook wrote:
> I assume this is due to some unhealthy arrangement of CONFIG items. I
> haven't had time to examine the original report...
This occurs with CONFIG_SECURITY off. The patch below fixes the problem.
>
> -Kees
>
> On Wed, Nov 5, 2014 at 3:16 AM, Fengguang Wu <fengguang.wu@intel.com> wrote:
>> Hi Casey,
>>
>> FYI, this error still remains in the updated tree.
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git lsm/stacking
>> commit 19ef36a6507555b231aef0498445148ac37aa2c4 ("LSM: Refactor existing LSM stacking")
>>
>>
>> +------------------------------------------------+------------+------------+
>> | | 644fb12c65 | 19ef36a650 |
>> +------------------------------------------------+------------+------------+
>> | boot_successes | 15 | 0 |
>> | early-boot-hang | 1 | |
>> | boot_failures | 0 | 15 |
>> | Kernel_panic-not_syncing:No_working_init_found | 0 | 15 |
>> | backtrace:panic | 0 | 15 |
>> +------------------------------------------------+------------+------------+
>>
>>
>> [ 14.083301] Starting init: /sbin/init exists but couldn't execute it (error -12)
>> [ 14.084391] Starting init: /etc/init exists but couldn't execute it (error -13)
>> [ 14.085300] Starting init: /bin/sh exists but couldn't execute it (error -12)
>> [ 14.085884] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
>> [ 14.086902] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.18.0-rc3-wl-00142-gb2eaffd #43
>> [ 14.087517] 00000000 00000000 b002df88 b17d4ee3 00000000 b002dfa0 b17d1b54 02178e76
>> [ 14.088230] 00000000 02178e76 b1bee500 b002dfac b17c8c30 b1aaf57d b002c000 b17e30e1
>> [ 14.088354] b17c8a3a 00000000 00000000 00000000 00000000 00000000 00000000 0000007b
>> [ 14.088354] Call Trace:
>> [ 14.088354] [<b17d4ee3>] dump_stack+0xb8/0x108
>> [ 14.088354] [<b17d1b54>] panic+0x13e/0x378
>> [ 14.088354] [<b17c8c30>] kernel_init+0x1f6/0x1fa
>> [ 14.088354] [<b17e30e1>] ret_from_kernel_thread+0x21/0x30
>> [ 14.088354] [<b17c8a3a>] ? rest_init+0x26f/0x26f
>> [ 14.088354] Kernel Offset: 0x0 from 0xb1000000 (relocation range: 0xb0000000-0xc6ffdfff)
>>
>> Thanks,
>> Fengguang
>>
>> _______________________________________________
>> LKP mailing list
>> LKP(a)linux.intel.com
>>
>>
include/linux/security.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/linux/security.h b/include/linux/security.h
index 5a6c839..5cd3e93 100644
--- a/include/linux/security.h
+++ b/include/linux/security.h
@@ -27,6 +27,7 @@
#include <linux/slab.h>
#include <linux/err.h>
#include <linux/string.h>
+#include <linux/mm.h>
struct linux_binprm;
struct cred;
@@ -1995,7 +1996,7 @@ static inline int security_settime(const struct timespec *ts,
static inline int security_vm_enough_memory_mm(struct mm_struct *mm, long pages)
{
- return cap_vm_enough_memory(mm, pages);
+ return __vm_enough_memory(mm, pages, cap_vm_enough_memory(mm, pages));
}
static inline int security_bprm_set_creds(struct linux_binprm *bprm)
next prev parent reply other threads:[~2014-11-12 0:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 11:16 [LSM] Kernel panic - not syncing: No working init found Fengguang Wu
2014-11-05 18:15 ` Kees Cook
2014-11-12 0:10 ` Casey Schaufler [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-17 6:08 Yuanhan Liu
2014-11-17 16:28 ` Casey Schaufler
2014-11-03 7:00 Fengguang Wu
2014-11-03 7:00 ` Fengguang Wu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5462A581.4050101@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=lkp@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.