From: Christoph Hellwig <hch@infradead.org>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: agruen@suse.de, xfs@oss.sgi.com, linux-arm@lists.arm.linux.org.uk
Subject: Re: [PATCH] libattr 2.4.32 arm eabi system call calling convention
Date: Thu, 30 Nov 2006 09:28:53 +0000 [thread overview]
Message-ID: <20061130092853.GB1534@infradead.org> (raw)
In-Reply-To: <20061130025459.GA23869@xi.wantstofly.org>
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.
next prev parent reply other threads:[~2006-11-30 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 2:54 [PATCH] libattr 2.4.32 arm eabi system call calling convention Lennert Buytenhek
2006-11-30 9:28 ` Christoph Hellwig [this message]
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=20061130092853.GB1534@infradead.org \
--to=hch@infradead.org \
--cc=agruen@suse.de \
--cc=buytenh@wantstofly.org \
--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