From: Andy Lutomirski <luto@amacapital.net>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: linux-crypto@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Andrew Lutomirski <luto@kernel.org>,
Stephan Mueller <smueller@chronox.de>
Subject: Re: Remaining crypto API regressions with CONFIG_VMAP_STACK
Date: Sun, 11 Dec 2016 11:13:55 -0800 [thread overview]
Message-ID: <CALCETrVBGPijiacbY-trdbgRPYC8grNrGA7TVu0xvxUaqud08w@mail.gmail.com> (raw)
In-Reply-To: <20161209230851.GB64048@google.com>
On Fri, Dec 9, 2016 at 3:08 PM, Eric Biggers <ebiggers3@gmail.com> wrote:
> In the 4.9 kernel, virtually-mapped stacks will be supported and enabled by
> default on x86_64. This has been exposing a number of problems in which
> on-stack buffers are being passed into the crypto API, which to support crypto
> accelerators operates on 'struct page' rather than on virtual memory.
>
> fs/cifs/smbencrypt.c:96
This should use crypto_cipher_encrypt_one(), I think.
--Andy
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-12-11 19:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 23:08 Eric Biggers
2016-12-10 5:25 ` Andy Lutomirski
2016-12-10 5:32 ` Herbert Xu
2016-12-10 6:03 ` [kernel-hardening] " Eric Biggers
2016-12-10 8:16 ` Herbert Xu
2016-12-10 8:39 ` Eric Biggers
2016-12-10 5:37 ` Herbert Xu
2016-12-10 6:30 ` [kernel-hardening] " Eric Biggers
2016-12-10 14:45 ` Jason A. Donenfeld
2016-12-10 17:48 ` Andy Lutomirski
2016-12-10 5:55 ` Eric Biggers
2016-12-11 19:13 ` Andy Lutomirski [this message]
2016-12-11 23:31 ` Eric Biggers
2016-12-12 18:34 ` Andy Lutomirski
2016-12-12 18:45 ` Gary R Hook
2016-12-13 3:39 ` Herbert Xu
2016-12-13 3:39 ` Herbert Xu
2016-12-13 17:06 ` Andy Lutomirski
2016-12-14 4:56 ` Herbert Xu
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=CALCETrVBGPijiacbY-trdbgRPYC8grNrGA7TVu0xvxUaqud08w@mail.gmail.com \
--to=luto@amacapital.net \
--cc=ebiggers3@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=smueller@chronox.de \
/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