Remove B_READ, B_WRITE and B_FREEBUF and replace them with a new

field in struct buf: b_iocmd.  The b_iocmd is enforced to have
exactly one bit set.

B_WRITE was bogusly defined as zero giving rise to obvious coding
mistakes.

Also eliminate the redundant struct buf flag B_CALL, it can just
as efficiently be done by comparing b_iodone to NULL.

Should you get a panic or drop into the debugger, complaining about
"b_iocmd", don't continue.  It is likely to write on your disk
where it should have been reading.

This change is a step in the direction towards a stackable BIO capability.

A lot of this patch were machine generated (Thanks to style(9) compliance!)

Vinum users:  Greg has not had time to test this yet, be careful.

1 files changed, 4 insertions, 4 deletions

diff --git a/sys/kern/vfs_default.c b/sys/kern/vfs_default.c
index bd7e9ca..35a3d09 100644
--- a/sys/kern/vfs_default.c
+++ b/sys/kern/vfs_default.c
@@ -153,10 +153,10 @@ vop_panic(struct vop_generic_args *ap)
  *	Strategy routine for VFS devices that have none.
  *
  *	B_ERROR and B_INVAL must be cleared prior to calling any strategy
- *	routine.  Typically this is done for a B_READ strategy call.  Typically
- *	B_INVAL is assumed to already be clear prior to a write and should not
- *	be cleared manually unless you just made the buffer invalid.  B_ERROR
- *	should be cleared either way.
+ *	routine.  Typically this is done for a BIO_READ strategy call.
+ *	Typically B_INVAL is assumed to already be clear prior to a write 
+ *	and should not be cleared manually unless you just made the buffer
+ *	invalid.  B_ERROR should be cleared either way.
  */
 
 static int