>>> pool_get(): use PR_WAITOK, not M_WAITOK (which happens to be PR_NOWAIT ..)
>>> XXX: not the first time this mistake has been made
>> find /usr/src/sys -name *.[ch"]" -exec grep -l pool_.*M_ "{"} ";"
>> I think we should use different values for the constants and, if
>> DIAGNOSTIC, assert that the constant is in fact in the correct
>> range.
> Could the compiler help here?  For example, if we used enums instead
> of plain int and macros?

No; C enums are too weakly typed.  If you really want the compiler to
help you you could do something like

typedef struct malloc_waitflag MALLOC_WAITFLAG;
struct malloc_waitflag { int v; };
#define M_WAITOK ((MALLOC_WAITFLAG){0})
#define M_NOWAIT ((MALLOC_WAITFLAG){1})
extern void *malloc(unsigned long, int type, MALLOC_WAITFLAG waitflag);

but this complicates all code that needs to check the flag, because it
has to check waitflag.v.  It also makes it more difficult to use
multiple flag bits.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B