# Re: \[PATCH for-5.14\] cryptoloop: add a deprecation warning

- From: Jens Axboe \<axboe@kernel.dk\>
- Date: 2021-08-27 16:48:13 
- List: linux-block
- Page: https://ratatoskr.run/linux-block/2021/08/6405078
- Thread: https://ratatoskr.run/linux-block/2021/08/6405070/t.md

```text
On 8/27/21 10:46 AM, Christoph Hellwig wrote:
> On Fri, Aug 27, 2021 at 10:43:53AM -0600, Jens Axboe wrote:
>> On 8/27/21 10:43 AM, Christoph Hellwig wrote:
>>> On Fri, Aug 27, 2021 at 10:42:59AM -0600, Jens Axboe wrote:
>>>> But what's the point? Why not just wait for 5.15, it's not like we're
>>>> in a mad dash to get it removed.
>>>
>>> Actually we kinda are :)
>>
>> Because?
> 
> It causes trouble by interacting with the actual loop driver people
> use in really weird ways, while beeing broken and not actually supported
> by userspace tools for about a decade.

I don't disagree with that, but that's not a new situation. Hence my
question on why there's this sudden mad rush to get it queued up for
removal, literally a few days before a kernel release.

-- 
Jens Axboe

```