From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <jbeulich@novell.com>
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, 8 Aug 2006 08:49:37 +0200 [thread overview]
Message-ID: <200608080849.38012.ak@suse.de> (raw)
In-Reply-To: <44D84D1F.76E4.0078.0@novell.com>
> >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.
-Andi
>
> >Could this be the problem?
> >
> >|ENTRY(sysenter_entry)
> >| CFI_STARTPROC simple
> >| CFI_DEF_CFA esp, 0
> >|==> CFI_REGISTER esp, ebp
> >| movl TSS_sysenter_esp0(%esp),%esp
> >|sysenter_past_esp:
next prev parent reply other threads:[~2006-08-08 6:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 0:39 2.6.18-rc3-g3b445eea BUG: warning at /usr/src/linux-git/kernel/cpu.c:51 Chuck Ebbert
2006-08-08 6:36 ` Jan Beulich
2006-08-08 6:49 ` Andi Kleen [this message]
2006-08-08 7:00 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
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=200608080849.38012.ak@suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=jbeulich@novell.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 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.