From: Herbert Xu <herbert@gondor.apana.org.au>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: Richard Weinberger <richard@nod.at>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-fscrypt@vger.kernel.org, David Gstir <david@sigma-star.at>
Subject: Re: fscrypt request_module() deadlock
Date: Wed, 19 Jul 2017 12:58:52 +0800 [thread overview]
Message-ID: <20170719045852.GA8653@gondor.apana.org.au> (raw)
In-Reply-To: <20170718231747.GA51535@gmail.com>
On Tue, Jul 18, 2017 at 04:17:47PM -0700, Eric Biggers wrote:
>
> While that should solve the problem, isn't it possible to actually have a module
> which supplies an algorithm like "xts(aes)"? In that case it wouldn't be
> desirable to instantiate the generic "xts" template.
Well, in the case where only xts and aes are built into the kernel
I think we have to use that instead of going to request_module as
otherwise we cannot avoid the dead-lock that is the subject of this
discussion.
If you want accelerated xts(aes) to work while building generic xts
and aes into the kernel then you should also build the accelerated
xts(aes) into the kernel (or load the manually once modules can be
loaded).
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2017-07-19 4:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 15:27 Richard Weinberger
2017-07-18 6:13 ` Herbert Xu
2017-07-18 23:17 ` Eric Biggers
2017-07-19 4:58 ` Herbert Xu [this message]
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=20170719045852.GA8653@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=david@sigma-star.at \
--cc=ebiggers3@gmail.com \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
/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
all inboxes | Powered by JetHome®