MIME-Version: 1.0
In-Reply-To: <20150225233414.GA3299@kria>
References: <1423778052-21038-1-git-send-email-dvlasenk@redhat.com>
 <1423778052-21038-2-git-send-email-dvlasenk@redhat.com> <CANaxB-zH5k1cKYMA+tOJxgLhenadJQmdtGktBE6EAUOExsqmEg@mail.gmail.com>
 <54EE1799.2000602@redhat.com> <CANaxB-xtTzwAw22LT1wBWD5V4yBcf5yv-YtvvOp3QtXG76hgTg@mail.gmail.com>
 <CALCETrWWHxqZo+aaDrPhJKEORMWG5Fn4-8Hq6B19yNX++GLb5g@mail.gmail.com>
 <54EE3E94.7060208@redhat.com> <CALCETrVFzm-nXwJSgjhLuHS6B1HT70Q0CsxybjJUmVAKALL5NA@mail.gmail.com>
 <20150225224055.GA3678@kria> <20150225233414.GA3299@kria>
From: Denys Vlasenko <vda.linux@googlemail.com>
Date: Thu, 26 Feb 2015 02:12:57 +0100
Message-ID: <CAK1hOcNY0v+_HeUSaq9hfJcb-NRLUtVNbbsjtrnE99MHg8OfPw@mail.gmail.com>
Subject: Re: [PATCH 2/3 v3] x86: entry_64.S: always allocate complete "struct pt_regs"
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: Andy Lutomirski <luto@amacapital.net>,
        Denys Vlasenko <dvlasenk@redhat.com>, Andrey Wagin <avagin@gmail.com>,
        Ingo Molnar <mingo@redhat.com>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Oleg Nesterov <oleg@redhat.com>, Borislav Petkov <bp@alien8.de>,
        "H. Peter Anvin" <hpa@zytor.com>,
        Frederic Weisbecker <fweisbec@gmail.com>, X86 ML <x86@kernel.org>,
        Alexei Starovoitov <ast@plumgrid.com>, Will Drewry <wad@chromium.org>,
        Kees Cook <keescook@chromium.org>, LKML <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1375
Lines: 29

On Thu, Feb 26, 2015 at 12:34 AM, Sabrina Dubroca <sd@queasysnail.net> wrote:
> 2015-02-25, 23:40:55 +0100, Sabrina Dubroca wrote:
>> I can run some userspace programs, but I have no idea what would be
>> helpful.
>> I can also try booting a real machine with archlinux/systemd tomorrow.
>
> I got a good boot out of kernels that normally fail.  I booted
> systemd's emergency shell and enabled a few services, in the same
> order they normally start.  journald started cleanly, but after that,
> every single command produced a "traps:" output and an "audit:" line.
>
> I disabled systemd-journald (chmod -x, because `systemctl disable`
> didn't really disable it), and now it boots, no "traps:" in the log.
> If I run it, everything fails again (zsh has traps for simply pressing
> enter on an empty cmd).

That's some progress!

It's strange how one process manages to affect everything else.

"If I run it, everything fails again". How do you run it? Directly,
or via systemd services mechanism?
If you just run it directly, can you try running it under
"strace -f -tt -oLOG"? Does it have the same effect? What's in the LOG?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/