[PATCH] docs: complete bumping minimal GNU Make version to 3.81

Commit 37d69ee3080811 ("docs: bump minimal GNU Make version to 3.81") changes one entry of GNU make version in the changes.rst, there's still one more entry saying that one need version 3.80. Fix that. Signed-off-by: Max Filippov --- Documentation/process/changes.rst | 2 +-

[PATCH] docs: bump minimal GNU Make version to 3.81

Recent kernel versions have broken compatibility with GNU Make version 3.80 here and there: $ git describe v4.11 $ make --version | head -1 GNU Make 3.80 $ make defconfig HOSTCC scripts/basic/fixdep scripts/Makefile.host:135: *** missing separator. Stop. make: *** [defconfig]

[RFC 06/10] dm: move dm-verity to generic async completion

dm-verity is starting async. crypto ops and waiting for them to complete. Move it over to generic code doing the same. Signed-off-by: Gilad Ben-Yossef --- drivers/md/dm-verity-target.c | 81 +++ drivers/md/dm-verity.h| 5 ---

[RFC 05/10] crypto: move testmgr to generic async completion

testmgr is starting async. crypto ops and waiting for them to complete. Move it over to generic code doing the same. This also provides a test of the generic crypto async. wait code. Signed-off-by: Gilad Ben-Yossef --- crypto/testmgr.c | 184

[RFC 09/10] ima: move to generic async completion

ima starts several async. crypto ops and waits for their completions. Move it over to generic code doing the same. Signed-off-by: Gilad Ben-Yossef --- security/integrity/ima/ima_crypto.c | 56 +++-- 1 file changed, 17 insertions(+), 39

[RFC 10/10] crypto: adapt api sample to use async. op wait

The code sample is waiting for an async. crypto op completion. Adapt sample to use the new generic infrastructure to do the same. Signed-off-by: Gilad Ben-Yossef --- Documentation/crypto/api-samples.rst | 52 +++- 1 file changed, 10

[RFC 08/10] cifs: move to generic async completion

cifs starts an async. crypto op and waits for their completion. Move it over to generic code doing the same. Signed-off-by: Gilad Ben-Yossef --- fs/cifs/smb2ops.c | 30 -- 1 file changed, 4 insertions(+), 26 deletions(-) diff --git

[RFC 03/10] crypto: move drbg to generic async completion

DRBG is starting an async. crypto op and waiting for it complete. Move it over to generic code doing the same. As part of the move the wait for op completion lost its _interruptible property. However, since each invocation is supposed to be short and since no other user in the kernel does the

[RFC 04/10] crypto: move gcm to generic async completion

gcm is starting an async. crypto op and waiting for it complete. Move it over to generic code doing the same. Signed-off-by: Gilad Ben-Yossef --- crypto/gcm.c | 34 ++ 1 file changed, 6 insertions(+), 28 deletions(-) diff --git

[RFC 02/10] crypto: move pub key to generic async completion

public_key_verify_signature() is starting an async crypto op and waiting for it to complete. Move it over to generic code doing the same. This also fixes a bug in which the code was passing the CRYPTO_TFM_REQ_MAY_BACKLOG flag to akcipher_request_set_callback() but was not correctly testing for

[RFC 01/10] crypto: factor async completion for general use

Invoking a possibly async. crypto op and waiting for completion while correctly handling backlog processing is a common task in the crypto API implementation and outside users of it. This patch re-factors one of the in crypto API implementation in preparation for using it across the board instead

[RFC 00/10] introduce crypto wait for async op function

Many users of kernel async. crypto services have a pattern of starting an async. crypto op and than using a completion to wait for it to end, resulting of the same code repeating itself in multiple places, sometime with errors. This patch aims to introduce a generic "wait for async. crypto op to

Re: [PATCH v5 13/32] x86/boot/e820: Add support to determine the E820 type of an address

On 5 May 2017 at 18:11, Borislav Petkov wrote: > On Tue, Apr 18, 2017 at 04:18:31PM -0500, Tom Lendacky wrote: >> Add a function that will return the E820 type associated with an address >> range. > > ... > >> @@ -110,9 +111,28 @@ bool __init e820__mapped_all(u64 start, u64 end,