From: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 15568] O_NONBLOCK is NOOP on block devices
Date: Tue, 11 May 2010 08:43:45 GMT [thread overview]
Message-ID: <201005110843.o4B8hjeZ003212@demeter.kernel.org> (raw)
In-Reply-To: <bug-15568-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=15568
--- Comment #3 from Petr Baudis <pasky-+ZI9xUNit7I@public.gmane.org> 2010-05-11 08:43:41 ---
Mike, I have not meant covering for some possible old versions, but covering
for future versions; if you know which version the man-page documents, you can
decide if you need to check further to see if your version has something new
there.
I don't know who was the original author describing O_NONBLOCK. I have never
really tended to misinterpret this myself, "Many file systems and disks were
considered to be fast enough that the implementation of O_NONBLOCK was deemed
unnecessary. So, O_NONBLOCK may not be available on files and/or disks" seemed
always rather clear to me, but I agree more detail and mentioning this at other
places than read(2) documentation as well would do good.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- 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:[~2010-05-11 8:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15568-11311@https.bugzilla.kernel.org/>
[not found] ` <bug-15568-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
2010-05-11 2:09 ` [Bug 15568] O_NONBLOCK is NOOP on block devices bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2010-05-11 3:38 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2010-05-11 8:43 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r [this message]
2010-05-12 22:22 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2012-07-05 16:15 ` 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=201005110843.o4B8hjeZ003212@demeter.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).