public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruen@suse.de>
To: Timothy Shimmin <tes@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Lennert Buytenhek <buytenh@wantstofly.org>,
	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, 7 Dec 2006 18:07:54 -0800	[thread overview]
Message-ID: <200612071807.55023.agruen@suse.de> (raw)
In-Reply-To: <20061130092853.GB1534@infradead.org>

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 :-)

  parent reply	other threads:[~2006-12-08  2:28 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
2006-11-30  9:38   ` Lennert Buytenhek
2006-12-08  2:07   ` Andreas Gruenbacher [this message]
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=200612071807.55023.agruen@suse.de \
    --to=agruen@suse.de \
    --cc=buytenh@wantstofly.org \
    --cc=hch@infradead.org \
    --cc=linux-arm@lists.arm.linux.org.uk \
    --cc=tes@sgi.com \
    --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