| To: | Lennert Buytenhek <buytenh@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] libattr 2.4.32 arm eabi system call calling convention |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Thu, 30 Nov 2006 09:28:53 +0000 |
| Cc: | agruen@xxxxxxx, xfs@xxxxxxxxxxx, linux-arm@xxxxxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <20061130025459.GA23869@xxxxxxxxxxxxxxxxx> |
| References: | <20061130025459.GA23869@xxxxxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.2.2i |
On Thu, Nov 30, 2006 at 03:54:59AM +0100, Lennert Buytenhek wrote: > 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. Please just rip out the direct syscalls. The days glibc provices all the xattr syscalls in sys/xattr.h, and libattr should just forward to those. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] libattr 2.4.32 arm eabi system call calling convention, Lennert Buytenhek |
|---|---|
| Next by Date: | Re: Review: Reduce in-core superblock lock contention near ENOSPC, Lachlan McIlroy |
| Previous by Thread: | [PATCH] libattr 2.4.32 arm eabi system call calling convention, Lennert Buytenhek |
| Next by Thread: | Re: [PATCH] libattr 2.4.32 arm eabi system call calling convention, Lennert Buytenhek |
| Indexes: | [Date] [Thread] [Top] [All Lists] |