mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: "Andi Kleen" <ak@suse.de>
Cc: "Chuck Ebbert" <76306.1226@compuserve.com>,
	"Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>,
	"Andrew Morton" <akpm@osdl.org>, "Dave Jones" <davej@redhat.com>,
	"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.18-rc3-g3b445eea BUG: warning at  /usr/src/linux-git/kernel/cpu.c:51
Date: Tue, 08 Aug 2006 08:00:24 +0100	[thread overview]
Message-ID: <44D852A8.76E4.0078.0@novell.com> (raw)
In-Reply-To: <200608080849.38012.ak@suse.de>

>>> Andi Kleen <ak@suse.de> 08.08.06 08:49 >>>
>
>> >include/asm-i386/unwind.h::arch_unw_user_mode():
>> >        return info->regs.eip < PAGE_OFFSET
>> >               || (info->regs.eip >= __fix_to_virt(FIX_VDSO)
>> >                    && info->regs.eip < __fix_to_virt(FIX_VDSO) + PAGE_SIZE)
>> >               || info->regs.esp < PAGE_OFFSET;
>> 
>> Hmm, indeed. Then I'm unclear what the problem might be here.
>
>That code will check for the vsyscall page, but sysenter_entry isn't 
>in the vsyscall page, but in the kernel proper.
>
>So it means the EIP never actually reached the vsyscall page. It should
>have gone up another level, but didn't.

I think we had seen sysenter_past_esp in the stack trace, so it did reach
that function. The next outer level should be the VDSO page, shouldn't it?

Jan

  reply	other threads:[~2006-08-08  6:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08  0:39 Chuck Ebbert
2006-08-08  6:36 ` Jan Beulich
2006-08-08  6:49   ` Andi Kleen
2006-08-08  7:00     ` Jan Beulich [this message]
2006-08-17 20:03 Chuck Ebbert

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=44D852A8.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=76306.1226@compuserve.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    /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

Powered by JetHome