Comment 9 for bug 1860535

@kmously sorry to not coming back earlier to that
I actually already did a verification some days ago when I setup a fresh LPAR with Eoan and having proposed enabled.
Since the patch/backport disables thin provisioning it's a regression test what's needed to see if something else got accidentally harmed.
For a different ticket I had to recompile a patched kernel (incl. headers, etc.) and everything worked fine and I didn't faced any issue.
Today in my morning I setup a z/VM guest on top with Eoan, enabled proposed, and updated also there to kernel 5.3.0-40 and explicitly wrote file crossing track boundaries and everything was fine (like expected, since ECKD thin provisioning was not active - and can't be activated anymore with that kernel, since the code was revoked).
Hence I successfully verified the Eoan proposed kernel (and with that adjusting the tags).