linux-kernel - Re: preempt bug in set_pmd

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]

Message-Id: <200803050228.34262.ak@suse.de>
Date:	Wed, 5 Mar 2008 02:28:34 +0100
From:	Andi Kleen <ak@...e.de>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: preempt bug in set_pmd_pfn?

On Wednesday 05 March 2008 01:19:36 Jeremy Fitzhardinge wrote:
> Andi Kleen wrote:
> > On Wednesday 05 March 2008 01:07:11 Jeremy Fitzhardinge wrote:
> >   
> >> Andi Kleen wrote:
> >>     
> >>>> Won't this leave a stale tlb on the old processor?
> >>>>     
> >>>>         
> >>> __set_fixmap should be only used in early boot, so it's always
> >>> on CPU 0
> >>>       
> >> vdso32-setup.c:map_compat_vdso() uses it to create the compat vdso 
> >> mapping, which typically happens on the first execve(),
> >>     
> >
> > First execve for 32bit binaries?
> >   
> 
> Yes, 32-bit kernel.

Ok I'm talking about 64bit. If you ask me something about 32bit please
always mention it especially.

> > Anyways __set_fixmap is __init and at the first  execve (unless you have initramfs) 
> > init.text should be already freed.
> 
> No, its not __init.  If it were I don't think there would have been much 
> booting going on for the last few months.

For 64bit my original statement was correct.

-Andi
--
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/