linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tip-bot for Oleg Nesterov <oleg@redhat.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
	oleg@redhat.com, tglx@linutronix.de
Subject: [tip:x86/urgent] x86: set_personality_ia32() misses force_personality32
Date: Tue, 16 Feb 2010 23:27:45 GMT	[thread overview]
Message-ID: <tip-1dfc76ec37a59018d8ed39152695ff27a434415b@git.kernel.org> (raw)
In-Reply-To: <20100216140213.GB16448@redhat.com>

Commit-ID:  1dfc76ec37a59018d8ed39152695ff27a434415b
Gitweb:     http://git.kernel.org/tip/1dfc76ec37a59018d8ed39152695ff27a434415b
Author:     Oleg Nesterov <oleg@redhat.com>
AuthorDate: Tue, 16 Feb 2010 15:02:13 +0100
Committer:  H. Peter Anvin <hpa@zytor.com>
CommitDate: Tue, 16 Feb 2010 09:44:30 -0800

x86: set_personality_ia32() misses force_personality32

05d43ed8a "x86: get rid of the insane TIF_ABI_PENDING bit" forgot
about force_personality32, fix.

Signed-off-by: Oleg Nesterov <oleg@redhat.com>
LKML-Reference: <20100216140213.GB16448@redhat.com>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
---
 arch/x86/kernel/process_64.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/arch/x86/kernel/process_64.c b/arch/x86/kernel/process_64.c
index 41a26a8..126f0b4 100644
--- a/arch/x86/kernel/process_64.c
+++ b/arch/x86/kernel/process_64.c
@@ -527,6 +527,7 @@ void set_personality_ia32(void)
 
 	/* Make sure to be in 32bit mode */
 	set_thread_flag(TIF_IA32);
+	current->personality |= force_personality32;
 
 	/* Prepare the first "return" to user space */
 	current_thread_info()->status |= TS_COMPAT;

  reply	other threads:[~2010-02-16 23:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-15 16:17 x86: get rid of the insane TIF_ABI_PENDING bit Oleg Nesterov
2010-02-15 16:23 ` H. Peter Anvin
2010-02-15 16:50   ` Oleg Nesterov
2010-02-15 18:06     ` H. Peter Anvin
2010-02-15 18:52       ` Oleg Nesterov
2010-02-15 19:07 ` H. Peter Anvin
2010-02-15 19:10 ` H. Peter Anvin
2010-02-15 19:41   ` Roland McGrath
2010-02-15 20:07     ` H. Peter Anvin
2010-02-15 21:14       ` Roland McGrath
2010-02-15 20:43     ` H. Peter Anvin
2010-02-15 21:05       ` Roland McGrath
2010-02-16 10:19       ` Oleg Nesterov
2010-02-16 10:23         ` Andi Kleen
2010-02-16 14:01           ` [PATCH 0/3] Was: " Oleg Nesterov
2010-02-16 14:02             ` [PATCH 1/3] x86: set_personality_ia32() misses force_personality32 Oleg Nesterov
2010-02-16 23:27               ` tip-bot for Oleg Nesterov [this message]
2010-02-16 14:02             ` [PATCH 2/3] x86: set_personality_ia32() abuses TS_COMPAT Oleg Nesterov
2010-02-16 15:40               ` Linus Torvalds
2010-02-16 17:16                 ` Oleg Nesterov
2010-02-16 17:38                   ` H. Peter Anvin
2010-02-16 17:44                 ` Oleg Nesterov
2010-02-16 17:51                   ` H. Peter Anvin
2010-02-17 15:40                     ` Oleg Nesterov
2010-02-16 18:43                   ` Linus Torvalds
2010-02-16 14:03             ` [PATCH 3/3] x86: ELF_PLAT_INIT() shouldn't worry about TIF_IA32 Oleg Nesterov
2010-02-16 14:24               ` Oleg Nesterov

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=tip-1dfc76ec37a59018d8ed39152695ff27a434415b@git.kernel.org \
    --to=oleg@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).