From: Christoph Hellwig <hch@infradead.org>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: fsetxattr() fails on a writable descriptor?
Date: Tue, 13 Oct 2009 19:58:05 -0400 [thread overview]
Message-ID: <20091013235805.GA18467@infradead.org> (raw)
In-Reply-To: <200909100014.10833@zmi.at>
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=xattr` 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. But if this was a new interface I would agree with you
that the behaviour is illogical.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-10-13 23:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1251987642.3855.36.camel@dhcp-lab-219.englab.brq.redhat.com>
[not found] ` <4AA1A3E6.2020606@draigBrady.com>
[not found] ` <87k50den1e.fsf@meyering.net>
[not found] ` <1252309787.3852.8.camel@dhcp-lab-219.englab.brq.redhat.com>
[not found] ` <4AA4C950.3080303@draigBrady.com>
[not found] ` <1252318482.3852.18.camel@dhcp-lab-219.englab.brq.redhat.com>
2009-09-08 11:29 ` fsetxattr() fails on a writable descriptor? Pádraig Brady
2009-09-08 18:40 ` Christoph Hellwig
2009-09-08 18:40 ` Christoph Hellwig
2009-09-09 21:23 ` Pádraig Brady
2009-09-09 21:23 ` Pádraig Brady
2009-09-09 22:14 ` Michael Monnerie
2009-10-13 23:58 ` Christoph Hellwig [this message]
2009-10-14 1:17 ` Michael Monnerie
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=20091013235805.GA18467@infradead.org \
--to=hch@infradead.org \
--cc=michael.monnerie@is.it-management.at \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.