public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Gutschke <markus@google.com>
To: linux-kernel@vger.kernel.org
Cc: Daniel Kegel <dkegel@google.com>, Russell King <rmk@arm.linux.org.uk>
Subject: [PATCH 1/1]: arm: _syscallX() macros must mark "memory" as clobbered
Date: Thu, 09 Mar 2006 15:38:56 -0800	[thread overview]
Message-ID: <4410BC90.1070108@google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 391 bytes --]

From: Markus Gutschke <markus@google.com>

While other platforms (including x86) have been fixed to mark memory as 
clobbered by _syscallX()'s, this bug has not yet been fixed for ARM. 
This patch adds the missing constraints and applies to version 2.6.15.6.

The bug can be tracked at http://bugzilla.kernel.org/show_bug.cgi?id=6205

Signed-off-by: Markus Gutschke <markus@google.com>

---

[-- Attachment #2: arm-unistd.h.diff --]
[-- Type: text/x-patch, Size: 1578 bytes --]

--- include/asm-arm/unistd.h.orig	2006-03-05 11:07:54.000000000 -0800
+++ include/asm-arm/unistd.h	2006-03-09 15:10:22.000000000 -0800
@@ -415,7 +415,7 @@
   __syscall(name)							\
 	: "=r" (__res_r0)						\
 	: "r" (__r0)							\
-	: "lr");							\
+	: "lr", "memory");						\
   __res = __res_r0;							\
   __syscall_return(type,__res);						\
 }
@@ -430,7 +430,7 @@
   __syscall(name)							\
 	: "=r" (__res_r0)						\
 	: "r" (__r0),"r" (__r1) 					\
-	: "lr");							\
+	: "lr", "memory");						\
   __res = __res_r0;							\
   __syscall_return(type,__res);						\
 }
@@ -447,7 +447,7 @@
   __syscall(name)							\
 	: "=r" (__res_r0)						\
 	: "r" (__r0),"r" (__r1),"r" (__r2)				\
-	: "lr");							\
+	: "lr", "memory");						\
   __res = __res_r0;							\
   __syscall_return(type,__res);						\
 }
@@ -465,7 +465,7 @@
   __syscall(name)							\
 	: "=r" (__res_r0)						\
 	: "r" (__r0),"r" (__r1),"r" (__r2),"r" (__r3)			\
-	: "lr");							\
+	: "lr", "memory");						\
   __res = __res_r0;							\
   __syscall_return(type,__res);						\
 }
@@ -484,7 +484,7 @@
   __syscall(name)							\
 	: "=r" (__res_r0)						\
 	: "r" (__r0),"r" (__r1),"r" (__r2),"r" (__r3),"r" (__r4)	\
-	: "lr");							\
+	: "lr", "memory");						\
   __res = __res_r0;							\
   __syscall_return(type,__res);						\
 }
@@ -503,7 +503,7 @@
   __syscall(name)							\
 	: "=r" (__res_r0)						\
 	: "r" (__r0),"r" (__r1),"r" (__r2),"r" (__r3), "r" (__r4),"r" (__r5)		\
-	: "lr");							\
+	: "lr", "memory");						\
   __res = __res_r0;							\
   __syscall_return(type,__res);						\
 }

             reply	other threads:[~2006-03-09 23:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-09 23:38 Markus Gutschke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-09 23:38 [PATCH 1/1]: arm: _syscallX() macros must mark "memory" as clobbered Markus Gutschke

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=4410BC90.1070108@google.com \
    --to=markus@google.com \
    --cc=dkegel@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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