linux-kernel - Re: 2.6.18-rc3-g3b445eea BUG: warning at /usr/src/linux-git/kernel/cpu.c:51

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 8 Aug 2006 08:49:37 +0200
From:	Andi Kleen <ak@...e.de>
To:	"Jan Beulich" <jbeulich@...ell.com>
Cc:	"Chuck Ebbert" <76306.1226@...puserve.com>,
	"Michal Piotrowski" <michal.k.k.piotrowski@...il.com>,
	"Andrew Morton" <akpm@...l.org>, "Dave Jones" <davej@...hat.com>,
	"linux-kernel" <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.18-rc3-g3b445eea BUG: warning at  /usr/src/linux-git/kernel/cpu.c:51


> >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:
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/