diff options
| author | Ralph Campbell <[email protected]> | 2018-02-01 00:20:30 +0000 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2018-02-01 01:18:40 +0000 |
| commit | 8d63e4cd62b2583c7efe64f2ede406b3f44983f6 (patch) | |
| tree | 9db2787ac3a37bd5ab9f08c5020158a8fc02d1b6 /scripts/gcc-plugins/randomize_layout_plugin.c | |
| parent | include/linux/mmzone.h: fix explanation of lower bits in the SPARSEMEM mem_ma... (diff) | |
| download | kernel-8d63e4cd62b2583c7efe64f2ede406b3f44983f6.tar.gz kernel-8d63e4cd62b2583c7efe64f2ede406b3f44983f6.zip | |
mm/hmm: fix uninitialized use of 'entry' in hmm_vma_walk_pmd()
The variable 'entry' is used before being initialized in
hmm_vma_walk_pmd().
No bad effect (beside performance hit) so !non_swap_entry(0) evaluate to
true which trigger a fault as if CPU was trying to access migrated
memory and migrate memory back from device memory to regular memory.
This function (hmm_vma_walk_pmd()) is called when a device driver tries
to populate its own page table. For migrated memory it should not
happen as the device driver should already have populated its page table
correctly during the migration.
Only case I can think of is multi-GPU where a second GPU triggers
migration back to regular memory. Again this would just result in a
performance hit, nothing bad would happen.
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ralph Campbell <[email protected]>
Signed-off-by: Jérôme Glisse <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'scripts/gcc-plugins/randomize_layout_plugin.c')
0 files changed, 0 insertions, 0 deletions