From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org
Subject: Re: [PATCH for-5.14] cryptoloop: add a deprecation warning
Date: Fri, 27 Aug 2021 10:48:09 -0600 [thread overview]
Message-ID: <5724b5a9-e8e9-d05d-83fe-8a0920261573@kernel.dk> (raw)
In-Reply-To: <20210827164637.GA26631@lst.de>
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
next prev parent reply other threads:[~2021-08-27 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 16:32 [PATCH for-5.14] cryptoloop: add a deprecation warning Christoph Hellwig
2021-08-27 16:37 ` Jens Axboe
2021-08-27 16:40 ` Christoph Hellwig
2021-08-27 16:42 ` Jens Axboe
2021-08-27 16:43 ` Christoph Hellwig
2021-08-27 16:43 ` Jens Axboe
2021-08-27 16:46 ` Christoph Hellwig
2021-08-27 16:48 ` Jens Axboe [this message]
2021-08-27 16:50 ` Christoph Hellwig
2021-08-27 16:52 ` Jens Axboe
2021-08-27 16:55 ` Christoph Hellwig
2021-08-27 16:57 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5724b5a9-e8e9-d05d-83fe-8a0920261573@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox