All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@amacapital.net>
To: x86@kernel.org, torvalds@linux-foundation.org,
	linux-kernel@vger.kernel.org
Cc: Andy Lutomirski <luto@amacapital.net>
Subject: [PATCH 0/2] x86: TLS regression fixes
Date: Thu, 22 Jan 2015 11:27:57 -0800	[thread overview]
Message-ID: <cover.1421954363.git.luto@amacapital.net> (raw)

The recent TLS hardening work broke at least one game.  This series
fixes it.  I'm not entirely happy with this series, but I'm far from
entirely happy with the TLS or LDT code in the first place.

Thoughts?

Andy Lutomirski (2):
  x86, tls, ldt: Stop checking lm in LDT_empty
  x86, tls: Interpret an all-zero struct user_desc as "no segment"

 arch/x86/include/asm/desc.h | 20 ++++++++++++++------
 arch/x86/kernel/tls.c       | 25 +++++++++++++++++++++++--
 2 files changed, 37 insertions(+), 8 deletions(-)

-- 
2.1.0


             reply	other threads:[~2015-01-22 19:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22 19:27 Andy Lutomirski [this message]
2015-01-22 19:27 ` [PATCH 1/2] x86, tls, ldt: Stop checking lm in LDT_empty Andy Lutomirski
2015-01-22 20:13   ` [tip:x86/urgent] " tip-bot for Andy Lutomirski
2015-01-22 19:27 ` [PATCH 2/2] x86, tls: Interpret an all-zero struct user_desc as "no segment" Andy Lutomirski
2015-01-22 19:47   ` Borislav Petkov
2015-01-22 20:12     ` Andy Lutomirski
2015-01-22 20:14   ` [tip:x86/urgent] x86, tls: Interpret an all-zero struct user_desc as %22no segment%22 tip-bot for Andy Lutomirski
2015-01-22 20:54   ` [tip:x86/urgent] x86, tls: Interpret an all-zero struct user_desc as "no segment" tip-bot for Andy Lutomirski
2015-01-22 19:56 ` [PATCH 0/2] x86: TLS regression fixes Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1421954363.git.luto@amacapital.net \
    --to=luto@amacapital.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    --subject='Re: [PATCH 0/2] x86: TLS regression fixes' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.