Philip Pokorny | 13 Jun 2007 19:18
Favicon

Re: tux-list Digest, Vol 29, Issue 7

tux-list-request <at> redhat.com wrote:

>i've released the tux3-2.6.18-1 Tux patch:
>
>   http://redhat.com/~mingo/TUX-patches/tux3-2.6.18-1
>
>this is a merge to v2.6.18, plus a few lockdep related fixes, and 64-bit 
>compiler warning eliminations.
>  
>
I was reading through this patch to catch up and saw a couple of things 
that look strange to me:

Index: linux/include/linux/errno.h
===================================================================
--- linux.orig/include/linux/errno.h
+++ linux/include/linux/errno.h
 <at>  <at>  -24,6 +24,9  <at>  <at> 
 #define EIOCBQUEUED	529	/* iocb queued, will get completion event */
 #define EIOCBRETRY	530	/* iocb queued, will trigger a retry */

+/* Defined for TUX async IO */
+#define EWOULDBLOCKIO	530	/* Would block due to block-IO */
+
 #endif

 #endif

Shouldn't EWOULDBLOCKIO have a unique value assigned to it?  In this 
case it's the same error code as EIOCBRETRY...
(Continue reading)


Gmane