<linux-fsdevel@xxxxxxxxxxxxxxx>,"open list:KERNEL SELFTEST FRAMEWORK" <linux-kselftest@xxxxxxxxxxxxxxx>,kvm list <kvm@xxxxxxxxxxxxxxx> From: hpa@xxxxxxxxx Message-ID: <E47D06A9-AFDA-4A9D-8539-9CC5AB19B395@xxxxxxxxx> On March 14, 2017 12:23:40 PM PDT, Andy Lutomirski <luto@xxxxxxxxxxxxxx> wrote: >On Tue, Mar 14, 2017 at 12:01 PM, H. Peter Anvin <hpa@xxxxxxxxx> 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@xxxxxxxxxx> >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. -- To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
