public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: fsetxattr() fails on a writable descriptor?
Date: Thu, 10 Sep 2009 00:14:10 +0200	[thread overview]
Message-ID: <200909100014.10833@zmi.at> (raw)
In-Reply-To: <4AA81CDB.8070509@draigBrady.com>

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? When you 
copy and want xattrs, and it fails sometimes, that's not what's 
expected. So if xattr is broken from day one and it should stay like 
this, should a bug report to "cp" be opened?
Do you get the same error when "rsync -aHAX"? I always use that to make 
a 1:1 copy, but if said problem exists that would be troublesome.

> [ch writes:]
> It seems a bit unusual, but I'm not sure changing it now
> is a good idea - the xattr support has been around for a long time.

I don't understand the inner depths, and didn't from the OP code, 
but a failing "cp" is not nice, too. Why shouldn't the behaviour be 
fixed?

mfg zmi
-- 
// 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

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-09-09 22:14 UTC|newest]

Thread overview: 6+ 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-09 21:23               ` Pádraig Brady
2009-09-09 22:14                 ` Michael Monnerie [this message]
2009-10-13 23:58                   ` Christoph Hellwig
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=200909100014.10833@zmi.at \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox