xfs
[Top] [All Lists]

Re: [PATCH] libattr 2.4.32 arm eabi system call calling convention

To: Timothy Shimmin <tes@xxxxxxx>
Subject: Re: [PATCH] libattr 2.4.32 arm eabi system call calling convention
From: Andreas Gruenbacher <agruen@xxxxxxx>
Date: Thu, 7 Dec 2006 18:07:54 -0800
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>, Lennert Buytenhek <buytenh@xxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, linux-arm@xxxxxxxxxxxxxxxxxxxxxx
In-reply-to: <20061130092853.GB1534@xxxxxxxxxxxxx>
Organization: SUSE Labs, Novell
References: <20061130025459.GA23869@xxxxxxxxxxxxxxxxx> <20061130092853.GB1534@xxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: KMail/1.9.5
Hello,

On Thursday 30 November 2006 01:28, Christoph Hellwig wrote:
> 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.

Yes, makes sense these days. Thanks for paying attention, Christoph.

Tim, who from the SGI side is taking care of the acl and attr packages in the 
xfs-cmds repository these days? Would you be doing this change, or are you 
waiting for a patch?

Thanks,
Andreas

PS. I hope we'll meet at linux.conf.au this January in Sydney, or in Melbourne 
some days later :-)


<Prev in Thread] Current Thread [Next in Thread>