From: Michael Monnerie <michael.monnerie@is.it-management.at>
Organization: it-management http://it-management.at
To: xfs@oss.sgi.com
Subject: Re: fsetxattr() fails on a writable descriptor?
Date: Wed, 14 Oct 2009 03:17:09 +0200
User-Agent: KMail/1.10.3 (Linux/2.6.31.3-ZMI; KDE/4.1.3; x86_64; ; )
References: <1251987642.3855.36.camel@dhcp-lab-219.englab.brq.redhat.com> <200909100014.10833@zmi.at> <20091013235805.GA18467@infradead.org>
In-Reply-To: <20091013235805.GA18467@infradead.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200910140317.09839@zmi.at>

On Mittwoch 14 Oktober 2009 Christoph Hellwig wrote:
> On Thu, Sep 10, 2009 at 12:14:10AM +0200, Michael Monnerie wrote:
> > On Mittwoch 09 September 2009 P?draig Brady wrote:
> > > The specific issue we have is that `cp --preserve=3Dxattr` gets an
> > > error when copying xattrs from a read only file. Since this has
> > > been an xattr issue since the start, we'll have to work around
> > > it.
> >
> > In that context I would call it a bug - shouldn't it be fixed?
>
> It seems pretty late for change behaviour that has been around
> since 2002. =A0But if this was a new interface I would agree with you
> that the behaviour is illogical.

I didn't restrict to fix xattr behaviour, but "cp" should be fixed.=20
After all, the bug exists since 2002, so "cp" should also work around it=20
to get it's own parameters right.

mfg zmi
=2D-=20
// Michael Monnerie, Ing.BSc    -----      http://it-management.at
// Tel: 0660 / 415 65 31                      .network.your.ideas.
// PGP Key:         "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38  500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net                  Key-ID: 1C1209B4