Re: [PATCH 1/2][RFC] add detailed error values to block layer

[Pavel Machek]

Hi!

> +enum {
> +	BLK_SUCCESS,
> +	BLK_ERR,		/* Generic error like -EIO */
> +	BLK_FATAL_DEV,		/* Fatal driver error */

	perhaps this should be fatal *device* error?

> +	BLK_FATAL_TRNSPT,	/* Fatal transport error */
> +	BLK_FATAL_DRV,		/* Fatal driver error */
> +	BLK_RETRY_DEV,		/* Device error, I/O may be retried */
> +	BLK_RETRY_TRNSPT,	/* Transport error, I/O may retried */
> +	BLK_RETRY_DRV,		/* Driver error, I/O may be retried */
> +};
> +
> +/*
>   * end_request() and friends. Must be called with the request queue spinlock
>   * acquired. All functions called within end_request() _must_be_ atomic.
>   *


-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/