> >> level drivers. It's better to have a consistent behavior for all devices.
> >
> >Oh, I suppose. I guess that because the target driver can reject a detach,
> >then you can your shorts wrapped your ankles when that happen.
> >
> >Still, it's the target driver who really should be deciding how important a
> >selection timeout is.
>
> Yeah, but idiosyncratic per-driver timeouts with no or idiosyncratic
> ways to change them leads to chaos.

Umm. Yeah, you're right.

>
>
> Here's a strawman: keep timeout information in one consistent place in
> the mid-layer, with
>
>   1)  A global default
>   2)  A callback for any hba instance to override the default for itself
>      (Matt's "policy"),  and  a config-time message letting the user know
>      the  HBA asserted its "policy".
>   3)  A way to force  wired-down defaults in a wired-down kernel config
>
> I'm thinking iSCSI...
>

I could live with this.

-matt