Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1548781 > unrolled thread
| Started by | Andy Lutomirski <luto@amacapital.net> |
|---|---|
| First post | 2016-12-31 02:40 +0100 |
| Last post | 2016-12-31 02:40 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [RFC 2/4] x86/thread_info: kill TIF_ADDR32 in favour of ADDR_LIMIT_32BIT Andy Lutomirski <luto@amacapital.net> - 2016-12-31 02:40 +0100
| From | Andy Lutomirski <luto@amacapital.net> |
|---|---|
| Date | 2016-12-31 02:40 +0100 |
| Subject | Re: [RFC 2/4] x86/thread_info: kill TIF_ADDR32 in favour of ADDR_LIMIT_32BIT |
| Message-ID | <sUgOl-4AL-1@gated-at.bofh.it> |
On Fri, Dec 30, 2016 at 7:56 AM, Dmitry Safonov <dsafonov@virtuozzo.com> wrote: > This thread flag is completely x86-specific, consolidate it with > ADDR_LIMIT_32BIT personality which is defined but not used on x86. > It will free one of thread flags and consolidate personality with > other arches. > After this commit ADDR_LIMIT_32BIT is set by the kernel automatically > in COMPAT_SET_PERSONALITY() for 32-bit ELF files and for 32-bit a.out. > It's cleared in SET_PERSONALITY() for 64-bit ELFs. I'm okay with this as a plain cleanup, but I'm not convinced that this is really the right long-term solution. See next email.
Back to top | Article view | linux.kernel
csiph-web