Re: [off-list] a path toward killing thread_info

From	Andy Lutomirski <luto@amacapital.net>
Newsgroups	linux.kernel
Subject	Re: [off-list] a path toward killing thread_info
Date	2016-06-18 01:30 +0200
Message-ID	<rLbn3-4A9-9@gated-at.bofh.it> (permalink)
References	<rLaKm-47q-5@gated-at.bofh.it> <rLb3H-4td-9@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Fri, Jun 17, 2016 at 4:04 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> On Fri, Jun 17, 2016 at 03:41:49PM -0700, Andy Lutomirski wrote:
>
>> PeterZ, I'm thinking of adding task_ti_flags_ptr to directly find the
>> ti flags word given a task_struct * so the scheduler can use it.  Does
>> that seem reasonable to you?
>
> What are you trying to do?  Merge task_struct and thread_info?

Merge thread_struct and thread_info, actually.  The only functional
thing that thread_info provides is a place for arches to stash stuff.
I also want to end the era of stack overflows smashing data structures
at a fixed offset.

If we kill thread_info (on x86, anyway) and enable virtually mapped
stacks (which I just emailed out v2 of), then a stack overflow will
just OOPS cleanly on x86 without clobbering anything.

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[off-list] a path toward killing thread_info Andy Lutomirski <luto@amacapital.net> - 2016-06-18 00:50 +0200
  Re: [off-list] a path toward killing thread_info Al Viro <viro@ZenIV.linux.org.uk> - 2016-06-18 01:10 +0200
    Re: [off-list] a path toward killing thread_info "H. Peter Anvin" <hpa@zytor.com> - 2016-06-18 01:20 +0200
      Re: [off-list] a path toward killing thread_info Benjamin Herrenschmidt <benh@kernel.crashing.org> - 2016-06-18 01:30 +0200
        Re: [off-list] a path toward killing thread_info "H. Peter Anvin" <hpa@zytor.com> - 2016-06-18 02:10 +0200
    Re: [off-list] a path toward killing thread_info Andy Lutomirski <luto@amacapital.net> - 2016-06-18 01:30 +0200

csiph-web