From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>, linux-block@vger.kernel.org
Subject: Re: [PATCH for-5.14] cryptoloop: add a deprecation warning
Date: Fri, 27 Aug 2021 18:40:51 +0200 [thread overview]
Message-ID: <20210827164051.GA26147@lst.de> (raw)
In-Reply-To: <59808096-34ff-151f-b7a2-f53d4262f00a@kernel.dk>
On Fri, Aug 27, 2021 at 10:37:41AM -0600, Jens Axboe wrote:
> On 8/27/21 10:32 AM, Christoph Hellwig wrote:
> > Support for cryptoloop has been officially marked broken and deprecated
> > in favor of dm-crypt (which supports the same broken algorithms if
> > needed) in Linux 2.6.4 (released in March 2004), and support for it has
> > been entirely removed from losetup in util-linux 2.23 (released in April
> > 2013). Add a warning and a deprecation schedule.
>
> Would probably look better to queue with the 5.15 patches at this point.
> Which then begs the question of whether we want to make the removal
> target 5.17 instead.
File locking also just managed to sneak in a short-term deprecation for
a very similar situation.
next prev parent reply other threads:[~2021-08-27 16:40 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 [this message]
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
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=20210827164051.GA26147@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--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