public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Eric Sesterhenn <snakebyte@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops with strace_test
Date: Wed, 30 Apr 2008 18:19:29 +0200	[thread overview]
Message-ID: <87k5ifgvse.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20080430121202.GD18314@alice> (Eric Sesterhenn's message of "Wed, 30 Apr 2008 14:12:02 +0200")

Eric Sesterhenn <snakebyte@gmx.de> writes:

> hi,
>
> running the strace_test from ltp 20080229 (ltp.sf.net) gives me
> two different oopses, so far i was not able to pinpoint to a specific
> testcase (propably because the strace uses the rng to decided what fails
> and what not) one oops is in iret_exc()

It is actually somewhere in the woods afterwards, iret_exc is just 
the last symbol before it.


>, the other in __copy_from_user_ll()
> The oopses dont happen with 2.6.24 so this appears to be a regression, i am starting
> a git-bisect, but this might take some time

I would try reverting the last two changesets of arch/x86/lib/usercopy_32.c

-Andi


  reply	other threads:[~2008-04-30 16:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 12:12 Oops with strace_test Eric Sesterhenn
2008-04-30 16:19 ` Andi Kleen [this message]
2008-05-05 10:00 ` Eric Sesterhenn
2008-05-05 18:00   ` Frederik Deweerdt
2008-05-06 12:10     ` Ingo Molnar
2008-05-06 15:07       ` Eric Sesterhenn
2008-05-07 10:36       ` Eric Sesterhenn
2008-05-07 13:36         ` Thomas Gleixner
2008-05-07 17:20           ` Eric Sesterhenn
2008-05-07 17:26             ` Thomas Gleixner
2008-05-07 19:09               ` Suresh Siddha
2008-05-07 21:46                 ` Eric Sesterhenn
2008-05-08 15:02                 ` Thomas Gleixner
2008-05-08 18:29                   ` Eric Sesterhenn

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=87k5ifgvse.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=snakebyte@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox