On Thu, 2019-02-07 at 12:57 -0800, Evan Green wrote: +AD4 Properly plumb out EOPNOTSUPP from loop driver operations, which may +AD4 get returned when for instance a discard operation is attempted but not +AD4 supported by the underlying block device. Before this change, everything +AD4 was reported in the log as an I/O error, which is scary and not +AD4 helpful in debugging. Reviewed-by: Bart Van Assche +ADw-bvanassche+AEA-acm.org+AD4
