linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: akpm@linux-foundation.org (akpm at linux-foundation.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch 2/2] arm, exec: remove redundant set_fs(USER_DS)
Date: Tue, 10 Jan 2012 15:40:06 -0800	[thread overview]
Message-ID: <20120110234007.2798B2000B9@hpza10.eem.corp.google.com> (raw)

From: Mathias Krause <minipli@googlemail.com>
Subject: arm, exec: remove redundant set_fs(USER_DS)

The address limit is already set in flush_old_exec() so this
set_fs(USER_DS) is redundant.

Signed-off-by: Mathias Krause <minipli@googlemail.com>
Cc: Russell King <rmk@arm.linux.org.uk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 arch/arm/include/asm/processor.h |    1 -
 1 file changed, 1 deletion(-)

diff -puN arch/arm/include/asm/processor.h~arm-exec-remove-redundant-set_fsuser_ds arch/arm/include/asm/processor.h
--- a/arch/arm/include/asm/processor.h~arm-exec-remove-redundant-set_fsuser_ds
+++ a/arch/arm/include/asm/processor.h
@@ -55,7 +55,6 @@ struct thread_struct {
 #define start_thread(regs,pc,sp)					\
 ({									\
 	unsigned long *stack = (unsigned long *)sp;			\
-	set_fs(USER_DS);						\
 	memset(regs->uregs, 0, sizeof(regs->uregs));			\
 	if (current->personality & ADDR_LIMIT_32BIT)			\
 		regs->ARM_cpsr = USR_MODE;				\
_

             reply	other threads:[~2012-01-10 23:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10 23:40 akpm at linux-foundation.org [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-02-08 20:42 [patch 2/2] arm, exec: remove redundant set_fs(USER_DS) akpm at linux-foundation.org
2011-11-15 22:51 akpm at linux-foundation.org
2011-07-28 20:50 akpm at linux-foundation.org

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=20120110234007.2798B2000B9@hpza10.eem.corp.google.com \
    --to=akpm@linux-foundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).