From: Mikulas Patocka <mpatocka@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, Mike Snitzer <msnitzer@redhat.com>,
dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Deadlock when using crypto API for block devices
Date: Fri, 24 Aug 2018 08:37:52 -0400 (EDT) [thread overview]
Message-ID: <alpine.LRH.2.02.1808240837120.11243@file01.intranet.prod.int.rdu2.redhat.com> (raw)
In-Reply-To: <20180824112435.ggizlqrymuibm6oo@gondor.apana.org.au>
On Fri, 24 Aug 2018, Herbert Xu wrote:
> On Fri, Aug 24, 2018 at 07:06:32AM -0400, Mikulas Patocka wrote:
> >
> > A quick search through the crypto code shows that ahash_save_req and
> > seqiv_aead_encrypt return -ENOMEM.
> >
> > Will you fix them?
>
> These only trigger for unaligned buffers. It would be much better
> if dm-crypt can ensure that the input/output is properly unaligned
> and if otherwise do the allocation in dm-crypt.
But we are relying here on an implementation detail and not on contract.
Mikulas
next prev parent reply other threads:[~2018-08-24 12:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 20:39 Deadlock when using crypto API for block devices Mikulas Patocka
2018-08-24 2:10 ` Herbert Xu
2018-08-24 11:06 ` Mikulas Patocka
2018-08-24 11:22 ` Mikulas Patocka
2018-08-24 11:25 ` Herbert Xu
2018-08-24 11:24 ` Herbert Xu
2018-08-24 12:37 ` Mikulas Patocka [this message]
2018-08-24 13:00 ` Mikulas Patocka
2018-08-24 13:21 ` Herbert Xu
2018-08-24 13:22 ` Herbert Xu
2018-08-24 16:02 ` Dave Watson
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=alpine.LRH.2.02.1808240837120.11243@file01.intranet.prod.int.rdu2.redhat.com \
--to=mpatocka@redhat.com \
--cc=davem@davemloft.net \
--cc=dm-devel@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msnitzer@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).