From: Andy Lutomirski <luto@amacapital.net>
To: Richard Weinberger <richard@nod.at>
Cc: "Richard Weinberger" <richard.weinberger@gmail.com>,
"Toralf Förster" <toralf.foerster@gmx.de>,
"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: 3.15: kernel BUG at kernel/auditsc.c:1525!
Date: Mon, 16 Jun 2014 10:32:12 -0700 [thread overview]
Message-ID: <CALCETrU+TmaEjPSHz1LwQJvVDp8fqoDs3O4b+3gS_ewthiwnMA@mail.gmail.com> (raw)
In-Reply-To: <539F297F.7010904@nod.at>
On Mon, Jun 16, 2014 at 10:29 AM, Richard Weinberger <richard@nod.at> wrote:
> Am 16.06.2014 19:25, schrieb Andy Lutomirski:
>> On Mon, Jun 16, 2014 at 10:21 AM, Richard Weinberger
>> <richard.weinberger@gmail.com> wrote:
>>> On Mon, Jun 16, 2014 at 6:33 PM, Toralf Förster <toralf.foerster@gmx.de> wrote:
>>>> $ cat syscall.c
>>>> #include <unistd.h>
>>>> #include <sys/syscall.h>
>>>> int main(){return syscall(1000)!=-1;}
>>
>> What architecture are you building for? On i386 and x86_64, 1000
>> shouldn't be big enough to trigger this.
>
> Toralf, is this an UML kernel?
>
I'm also interested in the userspace architecture. If it's x32
userspace, then I'm not surprised that there's a problem.
--Andy
> Thanks,
> //richard
--
Andy Lutomirski
AMA Capital Management, LLC
next prev parent reply other threads:[~2014-06-16 17:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 16:33 3.15: kernel BUG at kernel/auditsc.c:1525! Toralf Förster
2014-06-16 17:21 ` Richard Weinberger
2014-06-16 17:25 ` Andy Lutomirski
2014-06-16 17:29 ` Richard Weinberger
2014-06-16 17:32 ` Andy Lutomirski [this message]
2014-06-16 17:36 ` Toralf Förster
2014-06-16 17:50 ` Andy Lutomirski
2014-06-16 17:59 ` Toralf Förster
2014-06-16 18:15 ` Andy Lutomirski
2014-06-16 18:21 ` Toralf Förster
2014-06-16 18:24 ` Andy Lutomirski
2014-06-16 18:36 ` Toralf Förster
2014-06-16 20:41 ` Toralf Förster
2014-06-16 20:43 ` Richard Weinberger
2014-06-16 21:35 ` Andy Lutomirski
2014-06-16 21:48 ` H. Peter Anvin
2014-06-16 21:54 ` Andy Lutomirski
2014-06-16 21:58 ` H. Peter Anvin
2014-06-16 22:00 ` Andy Lutomirski
2014-06-20 15:41 ` Andy Lutomirski
2014-06-20 17:35 ` Toralf Förster
2014-06-23 21:04 ` Josh Boyer
2014-06-23 21:22 ` [PATCH] x86_32,entry: Do syscall exit work on badsys (CVE-2014-4508) Andy Lutomirski
2014-06-23 22:18 ` [tip:x86/urgent] x86_32, entry: Do syscall exit work on badsys ( CVE-2014-4508) tip-bot for Andy Lutomirski
2014-06-24 10:51 ` [PATCH] x86_32,entry: Do syscall exit work on badsys (CVE-2014-4508) Borislav Petkov
2014-06-24 20:53 ` Andy Lutomirski
2014-06-24 21:18 ` Borislav Petkov
2014-07-01 10:52 ` Quentin Casasnovas
2014-07-01 14:14 ` Andy Lutomirski
2014-06-17 15:38 ` 3.15: kernel BUG at kernel/auditsc.c:1525! Toralf Förster
2014-06-17 16:19 ` Andy Lutomirski
2014-06-20 4:44 ` Fwd: " Andy Lutomirski
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=CALCETrU+TmaEjPSHz1LwQJvVDp8fqoDs3O4b+3gS_ewthiwnMA@mail.gmail.com \
--to=luto@amacapital.net \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
--cc=richard@nod.at \
--cc=toralf.foerster@gmx.de \
/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.