It took 14 steps, but finally here is the possible culprit:
19809c2da28aee5860ad9a2eff760730a0710df0 is the first bad commit
commit 19809c2da28aee5860ad9a2eff760730a0710df0
Author: Michal Hocko <email address hidden>
Date: Mon May 8 15:57:44 2017 -0700
mm, vmalloc: use __GFP_HIGHMEM implicitly
__vmalloc* allows users to provide gfp flags for the underlying
allocation. This API is quite popular
The only problem is that many people are not aware that they really want
to give __GFP_HIGHMEM along with other flags because there is really no
reason to consume precious lowmemory on CONFIG_HIGHMEM systems for pages
which are mapped to the kernel vmalloc space. About half of users don't
use this flag, though. This signals that we make the API unnecessarily
too complex.
This patch simply uses __GFP_HIGHMEM implicitly when allocating pages to
be mapped to the vmalloc space. Current users which add __GFP_HIGHMEM
are simplified and drop the flag.
:040000 040000 5cdc1c298cd62f74b76602846ce13ef386b06f22 d35baa52e7f078b35eb659fe2926c20c0867ed9e M arch
:040000 040000 045c832d50bf5255b42bdb0f28b09d36087a10eb 72610cae50071293567c229360546df0b99baae4 M drivers
:040000 040000 11f420f52bd9613ce1a1b0b01e3cbbd287a7b729 d3b957b5a886ba12041462588c323521961f368e M fs
:040000 040000 035a87f5c946730440625485bab4283ba03cbf3a 311929864121b80809596cc34d36b83bd6b8b9a6 M include
:040000 040000 46bcc13bebdc7f704db764542b6fae0a6362f64d c5674e6547e15e4a879576971fab242e1513e7e2 M kernel
:040000 040000 e11579b380817b207dd328539bbfa23723d7af95 ffc174b7261fcffcd52bfac24994469ccf5c7d12 M mm
:040000 040000 8357adc979b4be710b3d295425ac8c7ecd31b34d 31058e41d6828bcd7a9c9daf7a45cfa46dcd3ec4 M net
It took 14 steps, but finally here is the possible culprit:
19809c2da28aee5 860ad9a2eff7607 30a0710df0 is the first bad commit 860ad9a2eff7607 30a0710df0
commit 19809c2da28aee5
Author: Michal Hocko <email address hidden>
Date: Mon May 8 15:57:44 2017 -0700
mm, vmalloc: use __GFP_HIGHMEM implicitly
__vmalloc* allows users to provide gfp flags for the underlying
allocation. This API is quite popular
$ git grep "=[[:space: ]]__vmalloc\ |return[ [:space: ]]*__vmalloc" | wc -l
77
The only problem is that many people are not aware that they really want
to give __GFP_HIGHMEM along with other flags because there is really no
reason to consume precious lowmemory on CONFIG_HIGHMEM systems for pages
which are mapped to the kernel vmalloc space. About half of users don't
use this flag, though. This signals that we make the API unnecessarily
too complex.
This patch simply uses __GFP_HIGHMEM implicitly when allocating pages to
be mapped to the vmalloc space. Current users which add __GFP_HIGHMEM
are simplified and drop the flag.
Link: http://<email address hidden>
Signed-off-by: Michal Hocko <email address hidden>
Reviewed-by: Matthew Wilcox <email address hidden>
Cc: Al Viro <email address hidden>
Cc: Vlastimil Babka <email address hidden>
Cc: David Rientjes <email address hidden>
Cc: Cristopher Lameter <email address hidden>
Signed-off-by: Andrew Morton <email address hidden>
Signed-off-by: Linus Torvalds <email address hidden>
:040000 040000 5cdc1c298cd62f7 4b76602846ce13e f386b06f22 d35baa52e7f078b 35eb659fe2926c2 0c0867ed9e M arch 5b42bdb0f28b09d 36087a10eb 72610cae5007129 3567c229360546d f0b99baae4 M drivers ce1a1b0b01e3cbb d287a7b729 d3b957b5a886ba1 2041462588c3235 21961f368e M fs 440625485bab428 3ba03cbf3a 311929864121b80 809596cc34d36b8 3bd6b8b9a6 M include 04db764542b6fae 0a6362f64d c5674e6547e15e4 a879576971fab24 2e1513e7e2 M kernel 07dd328539bbfa2 3723d7af95 ffc174b7261fcff cd52bfac2499446 9ccf5c7d12 M mm 10b3d295425ac8c 7ecd31b34d 31058e41d6828bc d7a9c9daf7a45cf a46dcd3ec4 M net
:040000 040000 045c832d50bf525
:040000 040000 11f420f52bd9613
:040000 040000 035a87f5c946730
:040000 040000 46bcc13bebdc7f7
:040000 040000 e11579b380817b2
:040000 040000 8357adc979b4be7