On Thu, Jul 04, 2024 at 11:49:56PM -0400, Martin K. Petersen wrote: > I had a couple of drives which supported the feature and several OEMs > were requesting it. However, it turned out that using 512e drives was a > much more elegant solution to this particular problem. So should we just drop the internval_exp member for now? It would simplify things a bit, but more importantly we wouldn't have to fix the !BLK_DEV_INTEGRITY case for strip/insert.
