public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Shaya Potter <spotter@cs.columbia.edu>
Cc: "Joseph D. Wagner" <theman@josephdwagner.info>,
	linux-fsdevel@vger.kernel.org
Subject: Re: Does sendfile() copy extended attributes?
Date: Mon, 15 Dec 2003 00:46:34 -0500	[thread overview]
Message-ID: <3FDD4ABA.9050003@pobox.com> (raw)
In-Reply-To: <1071466993.13226.46.camel@zaphod>

Shaya Potter wrote:
> On Sun, 2003-12-14 at 12:39, Joseph D. Wagner wrote:
> 
>>I want to use sendfile() to completely copy a file so that the copy is an 
>>EXACT, INDISTINGUISHABLE duplicate of the original.
>>
>>Hence, I need to know if sendfile() copies the extended attributes in 
>>addition to the file itself.
>>
>>While I have your attention, does sendfile() also copy the inode attributes 
>>(i.e. secure delete, compressed, etc.)?
> 
> 
> sendfile acting as a sys_copy() is a 2.4 unsupported behavior.  It
> doesn't work on 2.6.


Have you tested this assertion lately?  :)

AFAIK file-file sendfile(2) was fixed in 2.6.

	Jeff




  reply	other threads:[~2003-12-15  5:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-14 17:39 Does sendfile() copy extended attributes? Joseph D. Wagner
2003-12-15  5:43 ` Shaya Potter
2003-12-15  5:46   ` Jeff Garzik [this message]
2003-12-15  5:49     ` Shaya Potter
2003-12-15  5:55       ` Jeff Garzik
2003-12-15  5:59         ` Shaya Potter
2003-12-15 17:16 ` Bryan Henderson
2003-12-15 20:15   ` Joseph D. Wagner
2003-12-15 21:28     ` Jamie Lokier
2003-12-16  4:28       ` Joseph D. Wagner
2003-12-19 16:37         ` maximilian attems
2003-12-20 12:19           ` Joseph D. Wagner
2003-12-20 20:40             ` Jamie Lokier
2003-12-21 11:01               ` Joseph D. Wagner
2003-12-21 11:50                 ` Jamie Lokier
2003-12-21 19:31                   ` Joseph D. Wagner
2003-12-21 19:44                     ` Shaya Potter
2003-12-21 19:51                       ` Jamie Lokier

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=3FDD4ABA.9050003@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=spotter@cs.columbia.edu \
    --cc=theman@josephdwagner.info \
    /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