[PATCH] document EINVAL on unaligned access

Robert Millan rmh@aybabtu.com
Tue Nov 15 09:42:00 GMT 2005


Hi,

On GNU/kFreeBSD, unaligned read/write on devices causes EINVAL.  This patch
documents it (in a generic way).

2005-11-15  Robert Millan  <robertmh@gnu.org>

        * manual/llio.texi (read, write): Document EINVAL on unaligned access.

-- 
Robert Millan
-------------- next part --------------

2005-11-15  Robert Millan  <robertmh@gnu.org>

	* manual/llio.texi (read, write): Document EINVAL on unaligned access.

diff -ur libc.old/manual/llio.texi libc/manual/llio.texi
--- libc.old/manual/llio.texi	2003-05-10 09:56:51.000000000 +0200
+++ libc/manual/llio.texi	2005-08-21 17:37:15.000000000 +0200
@@ -368,6 +368,11 @@
 the signal is being blocked or ignored, or because the process group is
 orphaned.  @xref{Job Control}, for more information about job control,
 and @ref{Signal Handling}, for information about signals.
+
+@item EINVAL
+In some systems, when reading from a character or block device, position
+and size offsets must be aligned to a particular block size.  This error
+indicates that the offsets were not properly aligned.
 @end table
 
 Please note that there is no function named @code{read64}.  This is not
@@ -515,6 +520,11 @@
 This error is returned when you try to write to a pipe or FIFO that
 isn't open for reading by any process.  When this happens, a @code{SIGPIPE}
 signal is also sent to the process; see @ref{Signal Handling}.
+
+@item EINVAL
+In some systems, when writing to a character or block device, position
+and size offsets must be aligned to a particular block size.  This error
+indicates that the offsets were not properly aligned.
 @end table
 
 Unless you have arranged to prevent @code{EINTR} failures, you should


More information about the Libc-alpha mailing list