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
| ||
|
Date: Wed, 15 Mar 2017 02:11:48 -0700 From: "H. Peter Anvin" <hpa@...or.com> To: Andy Lutomirski <luto@...capital.net> CC: Kyle Huey <me@...ehuey.com>, "Robert O'Callahan" <robert@...llahan.org>, Thomas Gleixner <tglx@...utronix.de>, Andy Lutomirski <luto@...nel.org>, Ingo Molnar <mingo@...hat.com>, X86 ML <x86@...nel.org>, Paolo Bonzini <pbonzini@...hat.com>, Radim Krčmář <rkrcmar@...hat.com>, Jeff Dike <jdike@...toit.com>, Richard Weinberger <richard@....at>, Alexander Viro <viro@...iv.linux.org.uk>, Shuah Khan <shuah@...nel.org>, Dave Hansen <dave.hansen@...ux.intel.com>, Borislav Petkov <bp@...e.de>, Peter Zijlstra <peterz@...radead.org>, Boris Ostrovsky <boris.ostrovsky@...cle.com>, Len Brown <len.brown@...el.com>, "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>, Dmitry Safonov <dsafonov@...tuozzo.com>, David Matlack <dmatlack@...gle.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "user-mode-linux-devel@...ts.sourceforge.net" <user-mode-linux-devel@...ts.sourceforge.net>, "open list:USER-MODE LINUX (UML)" <user-mode-linux-user@...ts.sourceforge.net>, Linux.FS.Devel@...or.com Subject: Re: [PATCH v10 6/7] x86/arch_prctl: Add ARCH_[GET|SET]_CPUID <linux-fsdevel@...r.kernel.org>,"open list:KERNEL SELFTEST FRAMEWORK" <linux-kselftest@...r.kernel.org>,kvm list <kvm@...r.kernel.org> From: hpa@...or.com Message-ID: <E47D06A9-AFDA-4A9D-8539-9CC5AB19B395@...or.com> On March 14, 2017 12:23:40 PM PDT, Andy Lutomirski <luto@...capital.net> wrote: >On Tue, Mar 14, 2017 at 12:01 PM, H. Peter Anvin <hpa@...or.com> wrote: >> and at least theoretically we >> could be indirecting though the ->stack pointer for every one if gcc >> can't tell it won't have changed (we really need to get thread_info >> moved into the task_struct allocation and away from the kernel stack, >> especially since on x86 the pointer is the same size as the vestigial >> structure it points to.) > >Solved by use of time machine: > >commit 15f4eae70d365bba26854c90b6002aaabb18c8aa >Author: Andy Lutomirski <luto@...nel.org> >Date: Tue Sep 13 14:29:25 2016 -0700 > > x86: Move thread_info into task_struct > > >:) My apologies, -ESTALEBRAINCACHE... -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Powered by blists - more mailing lists