From: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 82841] sendfile doesn't work with O_APPEND
Date: Fri, 22 Aug 2014 02:18:48 +0000 [thread overview]
Message-ID: <bug-82841-11311-2L93ud9lfY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-82841-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=82841
--- Comment #2 from Jason Newton <nevion-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
(In reply to Alan from comment #1)
> O_APPEND is not supported for sendfile().
>
> It's documented in the splice() manual page but not for sendfile so I've
> moved this to a documentation bug
OK so this quirk was not out in the open in documentation - before I opened
this bug report I read a few years old discussion:
http://fixunix.com/kernel/543017-splice-vs-o_append.html
Most of what they're talking about is splice, not sendfile. They might use the
same implementation but sendfile should be O_APPEND safe as there is no
specifiable offset in the output filedescriptor. Is there a reason to not
support it?
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-08-22 2:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-82841-11311@https.bugzilla.kernel.org/>
[not found] ` <bug-82841-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
2014-08-21 15:22 ` [Bug 82841] sendfile doesn't work with O_APPEND bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2014-08-22 2:18 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r [this message]
2014-08-22 8:31 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2015-05-05 9:13 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
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=bug-82841-11311-2L93ud9lfY@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon-590eeb7gvniway/ihj7yzeb+6bgklq7r@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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.