On Mon, Aug 05, 2019 at 08:12:58AM -0700, Darrick J. Wong wrote: > > returned. And IIRC, iomap is the only interface now that cares about issuing a > > warning. > > > > I think the *best* we could do here, is to make the new bmap() to issue the same > > kind of WARN() iomap does, but we can't really change the end result. > > I'd rather we break legacy code than corrupt filesystems. This particular patch should keep existing behavior as is, as the intent is to not change functionality. Throwing in another patch to have saner error behavior now that we have a saner in-kernel interface that cleary documents what it is breaking and why on the other hand sounds like a very good idea.
