sendfile(2) behaviour has changed ?

From: Zilvinas Valinskas (zilvinas@gemtek.lt)
Date: Wed Oct 16 2002 - 03:49:08 EST

Next message: Melkor Ainur: "user space virtual address to a vm_area_struct"
Previous message: Oleg Drokin: "UML and 2.5.43"
Next in thread: Matti Aarnio: "Re: sendfile(2) behaviour has changed ?"
Reply: Matti Aarnio: "Re: sendfile(2) behaviour has changed ?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This sample code copies a file using sendfile(2) call works just fine on
2.2.x and 2.4.x kernels. On 2.5.x kernels (not sure starting which
version) it stopped working. Program terminates with EINVAL error.

$ ./sendfile
sendfile: Invalid argument

Is this expected behaviour ? that sendfile(2) on 2.5.4x linux kernel requires
socket as an output fd paramter ?

Was it ever legal to copy file(s) on filesystem using sendfile(2) ?
(which was kindda nice feature ... )

text/x-csrc attachment: sendfile.c

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Melkor Ainur: "user space virtual address to a vm_area_struct"
Previous message: Oleg Drokin: "UML and 2.5.43"
Next in thread: Matti Aarnio: "Re: sendfile(2) behaviour has changed ?"
Reply: Matti Aarnio: "Re: sendfile(2) behaviour has changed ?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Wed Oct 23 2002 - 22:00:27 EST