From: Eric Paris <eparis@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Richard Guy Briggs <rgb@redhat.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
x86@kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
linux-audit@redhat.com, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Regression: audit: x86: drop arch from __audit_syscall_entry() interface
Date: Wed, 22 Oct 2014 18:44:33 -0400 [thread overview]
Message-ID: <1414017873.30946.105.camel@localhost> (raw)
In-Reply-To: <544824F3.9000808@zytor.com>
On Wed, 2014-10-22 at 14:43 -0700, H. Peter Anvin wrote:
> On 10/22/2014 02:38 PM, Eric Paris wrote:
> >
> > It was sent, numerous times, to the x86 list for reviews, and lived in
> > -next for 2 complete devel cycles without a complaint. I'm trying to
> > get an i386 system to test a fix. But yes, it's total crap.
> >
>
> You don't need an i386 system -- you can install an i386 distro on an
> x86-64 system, or in KVM.
So I might still be an idiot, because I still haven't gotten a working
kernel. But I can't get Linus' latest not panic even without
CONFIG_AUDITSYSCALL. I kept blaming myself for not fixing this problem,
but reverting the patch like the reporter didn't give me bootable
kernels either.
I just jumped back in time and am looking to get anything I build to
boot...
WARNING: multiple messages have this Message-ID (diff)
From: Eric Paris <eparis@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Paulo Zanoni <przanoni@gmail.com>,
Richard Guy Briggs <rgb@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-audit@redhat.com,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Daniel Vetter <daniel@ffwll.ch>
Subject: Re: Regression: audit: x86: drop arch from __audit_syscall_entry() interface
Date: Wed, 22 Oct 2014 18:44:33 -0400 [thread overview]
Message-ID: <1414017873.30946.105.camel@localhost> (raw)
In-Reply-To: <544824F3.9000808@zytor.com>
On Wed, 2014-10-22 at 14:43 -0700, H. Peter Anvin wrote:
> On 10/22/2014 02:38 PM, Eric Paris wrote:
> >
> > It was sent, numerous times, to the x86 list for reviews, and lived in
> > -next for 2 complete devel cycles without a complaint. I'm trying to
> > get an i386 system to test a fix. But yes, it's total crap.
> >
>
> You don't need an i386 system -- you can install an i386 distro on an
> x86-64 system, or in KVM.
So I might still be an idiot, because I still haven't gotten a working
kernel. But I can't get Linus' latest not panic even without
CONFIG_AUDITSYSCALL. I kept blaming myself for not fixing this problem,
but reverting the patch like the reporter didn't give me bootable
kernels either.
I just jumped back in time and am looking to get anything I build to
boot...
next prev parent reply other threads:[~2014-10-22 22:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 18:08 Regression: audit: x86: drop arch from __audit_syscall_entry() interface Paulo Zanoni
2014-10-22 18:08 ` Paulo Zanoni
2014-10-22 18:23 ` Eric Paris
2014-10-22 18:23 ` Eric Paris
2014-10-22 19:01 ` Andy Lutomirski
2014-10-22 19:01 ` Andy Lutomirski
2014-10-22 19:16 ` Richard Guy Briggs
2014-10-22 19:16 ` Richard Guy Briggs
2014-10-22 19:20 ` Andy Lutomirski
2014-10-22 19:20 ` Andy Lutomirski
2014-10-22 21:36 ` Thomas Gleixner
2014-10-22 21:38 ` Eric Paris
2014-10-22 21:38 ` Eric Paris
2014-10-22 21:43 ` H. Peter Anvin
2014-10-22 21:44 ` Eric Paris
2014-10-22 21:44 ` Eric Paris
2014-10-22 22:44 ` Eric Paris [this message]
2014-10-22 22:44 ` Eric Paris
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=1414017873.30946.105.camel@localhost \
--to=eparis@redhat.com \
--cc=hpa@zytor.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rgb@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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.