Thread (9 messages) 9 messages, 3 authors, 2020-03-26

Re: [PATCH RESEND 1/2] loop: Report EOPNOTSUPP properly

From: Christoph Hellwig <hch@infradead.org>
Date: 2020-03-26 15:55:59

On Thu, Mar 26, 2020 at 08:51:21AM -0700, Evan Green wrote:
On Thu, Mar 26, 2020 at 7:53 AM Christoph Hellwig [off-list ref] wrote:
quoted
On Tue, Mar 17, 2020 at 05:51:06PM +0100, Andrzej Pietrasiewicz wrote:
quoted
From: Evan Green <redacted>

Properly plumb out EOPNOTSUPP from loop driver operations, which may
get returned when for instance a discard operation is attempted but not
supported by the underlying block device. Before this change, everything
was reported in the log as an I/O error, which is scary and not
helpful in debugging.
This really should be using errno_to_blk_status.
I had that here in v7:
https://lore.kernel.org/lkml/20191114235008.185111-1-evgreen@chromium.org/ (local)
Well, it wasn't in the version you sent the ping for..
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help