From: Andy Lutomirski <luto@amacapital.net>
To: Eric Paris <eparis@redhat.com>, Paulo Zanoni <przanoni@gmail.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>,
linux-audit@redhat.com, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: Regression: audit: x86: drop arch from __audit_syscall_entry() interface
Date: Wed, 22 Oct 2014 12:01:36 -0700 [thread overview]
Message-ID: <5447FF10.3060506@amacapital.net> (raw)
In-Reply-To: <1414002190.30946.95.camel@localhost>
On 10/22/2014 11:23 AM, Eric Paris wrote:
> That's really serious. Looking now.
>
> On Wed, 2014-10-22 at 16:08 -0200, Paulo Zanoni wrote:
>> Hi
>>
>> (Cc'ing everybody mentioned in the original patch)
>>
>> I work for Intel, on our Linux Graphics driver - aka i915.ko - and our
>> QA team recently reported a regression on:
>>
>> commit b4f0d3755c5e9cc86292d5fd78261903b4f23d4a
>> Author: Richard Guy Briggs
>> Date: Tue Mar 4 10:38:06 2014 -0500
>> audit: x86: drop arch from __audit_syscall_entry() interface
>>
>> According to our QA, their i386 machine doesn't boot anymore. I tried
>> to write my own revert for the patch, asked QA to test, and they
>> confirmed it "solves" the problem.
>>
>> Here are the details of QA' s bug report:
>> https://bugs.freedesktop.org/show_bug.cgi?id=85277 .
>>
>> The trees our QA tests are the development trees from i915.ko:
>> http://cgit.freedesktop.org/drm-intel?h=drm-intel-fixes .
>>
>> I tried searching for other bug reports on the same patch, but
>> couldn't find any. Forgive me if this bug was already reported.
>>
>> Feel free to continue this discussion on the bugzilla report if you want.
This piece:
movl %esi,4(%esp) /* 5th arg: 4th syscall arg */
movl %edx,(%esp) /* 4th arg: 3rd syscall arg */
looks like it's overwriting syscall arguments.
This is clearly fixable, but an even better fix would be to drop the asm
entirely and switch to two-phase tracing. Want to do it? I can test
the seccomp bits if you switch over the asm :)
--Andy
WARNING: multiple messages have this Message-ID (diff)
From: Andy Lutomirski <luto@amacapital.net>
To: Eric Paris <eparis@redhat.com>, Paulo Zanoni <przanoni@gmail.com>
Cc: linux-audit@redhat.com, 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>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Regression: audit: x86: drop arch from __audit_syscall_entry() interface
Date: Wed, 22 Oct 2014 12:01:36 -0700 [thread overview]
Message-ID: <5447FF10.3060506@amacapital.net> (raw)
In-Reply-To: <1414002190.30946.95.camel@localhost>
On 10/22/2014 11:23 AM, Eric Paris wrote:
> That's really serious. Looking now.
>
> On Wed, 2014-10-22 at 16:08 -0200, Paulo Zanoni wrote:
>> Hi
>>
>> (Cc'ing everybody mentioned in the original patch)
>>
>> I work for Intel, on our Linux Graphics driver - aka i915.ko - and our
>> QA team recently reported a regression on:
>>
>> commit b4f0d3755c5e9cc86292d5fd78261903b4f23d4a
>> Author: Richard Guy Briggs
>> Date: Tue Mar 4 10:38:06 2014 -0500
>> audit: x86: drop arch from __audit_syscall_entry() interface
>>
>> According to our QA, their i386 machine doesn't boot anymore. I tried
>> to write my own revert for the patch, asked QA to test, and they
>> confirmed it "solves" the problem.
>>
>> Here are the details of QA' s bug report:
>> https://bugs.freedesktop.org/show_bug.cgi?id=85277 .
>>
>> The trees our QA tests are the development trees from i915.ko:
>> http://cgit.freedesktop.org/drm-intel?h=drm-intel-fixes .
>>
>> I tried searching for other bug reports on the same patch, but
>> couldn't find any. Forgive me if this bug was already reported.
>>
>> Feel free to continue this discussion on the bugzilla report if you want.
This piece:
movl %esi,4(%esp) /* 5th arg: 4th syscall arg */
movl %edx,(%esp) /* 4th arg: 3rd syscall arg */
looks like it's overwriting syscall arguments.
This is clearly fixable, but an even better fix would be to drop the asm
entirely and switch to two-phase tracing. Want to do it? I can test
the seccomp bits if you switch over the asm :)
--Andy
next prev parent reply other threads:[~2014-10-22 19:01 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 [this message]
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
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=5447FF10.3060506@amacapital.net \
--to=luto@amacapital.net \
--cc=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=przanoni@gmail.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.