public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Lennert Buytenhek <buytenh@wantstofly.org>
To: agruen@suse.de, xfs@oss.sgi.com
Cc: linux-arm@lists.arm.linux.org.uk
Subject: [PATCH] libattr 2.4.32 arm eabi system call calling convention
Date: Thu, 30 Nov 2006 03:54:59 +0100	[thread overview]
Message-ID: <20061130025459.GA23869@xi.wantstofly.org> (raw)

When building for EABI, a different system call calling convention is
used where system calls are numbered starting from zero, not 0x900000
as in the old ABI.  This was causing 'ls -al' with an ls binary that
was built with xattr support to SIGILL.


--- attr-2.4.32/libattr/syscalls.c.orig	2006-11-30 03:34:25.000000000 +0100
+++ attr-2.4.32/libattr/syscalls.c	2006-11-30 03:35:12.000000000 +0100
@@ -110,7 +110,11 @@
 # define __NR_fremovexattr	235
 #elif defined (__arm__)
 # define HAVE_XATTR_SYSCALLS 1
-# define __NR_SYSCALL_BASE 0x900000
+# if defined(__ARM_EABI__) || defined(__thumb__)
+#  define __NR_SYSCALL_BASE 0
+# else
+#  define __NR_SYSCALL_BASE 0x900000
+# endif
 # define __NR_setxattr		(__NR_SYSCALL_BASE+226)
 # define __NR_lsetxattr		(__NR_SYSCALL_BASE+227)
 # define __NR_fsetxattr		(__NR_SYSCALL_BASE+228)

-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
FAQ:        http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette:  http://www.arm.linux.org.uk/mailinglists/etiquette.php

             reply	other threads:[~2006-11-30  3:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-30  2:54 Lennert Buytenhek [this message]
2006-11-30  9:28 ` [PATCH] libattr 2.4.32 arm eabi system call calling convention Christoph Hellwig
2006-11-30  9:38   ` Lennert Buytenhek
2006-12-08  2:07   ` Andreas Gruenbacher
2006-12-08  2:55     ` Nathan Scott

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=20061130025459.GA23869@xi.wantstofly.org \
    --to=buytenh@wantstofly.org \
    --cc=agruen@suse.de \
    --cc=linux-arm@lists.arm.linux.org.uk \
    --cc=xfs@oss.sgi.com \
    /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