From: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 94271] fcntl.2 and pipe.7 need to say more about use of O_ASYNC
Date: Fri, 11 Mar 2016 06:59:07 +0000 [thread overview]
Message-ID: <bug-94271-11311-KOxytgCiZF@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-94271-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=94271
Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Resolution|--- |CODE_FIX
--- Comment #1 from Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
I reworked a paragraph in fcntl(2) to:
As well as setting the file descriptor owner, one must
also enable generation of signals on the file descrip‐
tor. This is done by using the fcntl() F_SETFL command
to set the O_ASYNC file status flag on the file descrip‐
tor. Subsequently, a SIGIO signal is sent whenever
input or output becomes possible on the file descriptor.
The fcntl() F_SETSIG command can be used to obtain
delivery of a signal other than SIGIO.
And a paragraph in pipe(7) to:
Setting the O_ASYNC flag for the read end of a pipe causes a
signal (SIGIO by default) to be generated when new input
becomes available on the pipe. The target for delivery of sig‐
nals must be set using the fcntl(2) F_SETOWN command. On
Linux, O_ASYNC is supported for pipes and FIFOs only since ker‐
nel 2.6.
I think that probably suffices(?). So, I'll close this bug.
--
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
prev parent reply other threads:[~2016-03-11 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 16:06 [Bug 94271] New: fcntl.2 and pipe.7 need to say more about use of O_ASYNC bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
[not found] ` <bug-94271-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
2016-03-11 6:59 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r [this message]
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-94271-11311-KOxytgCiZF@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.