Hello, Jeff, Douglas and Jens.

I've been trying to port the ordered reimplementation patchset over to 
post-2.6.15 head of blk tree.  This tree now contains PIO and mode sense 
improvements for libata.

ATA FUA is interesting in that it's supported only for multisector PIO 
and DMA protocols.  There is no ATA_CMD_PIO_WRITE_FUA_EXT.  So, when 
generating mode sense page, the status of FUA supported bit is dependent 
on the configured transfer mode.  As there doesn't seem to be dynamic 
transfer mode configuration yet, I'm thinking of simply passing ap or 
device down to mode sense functions and use it to report FUA status. 
How does that sound?

If dynamic transport configuration is implemented in the future (from EH 
or explicit user input), this FUA bit will go on and off depending on 
transfer mode.  Ugh... It seems that we'll need a way to raise UA for 
configuration change and trigger revalidation of SCSI disk device.

-- 
tejun