diff options
| author | David Rientjes <rientjes@google.com> | 2012-11-16 23:14:48 +0100 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2012-11-16 23:33:03 +0100 |
| commit | 1756954c61cb5c97c618ccb366482b9c1f891d6d (patch) | |
| tree | 86a8ab12560d600fa5459218979e72827e0311f5 /mm/memcontrol.c | |
| parent | mm: add anon_vma_lock to validate_mm() (diff) | |
| download | linux-1756954c61cb5c97c618ccb366482b9c1f891d6d.tar.xz linux-1756954c61cb5c97c618ccb366482b9c1f891d6d.zip | |
mm: fix build warning for uninitialized value
do_wp_page() sets mmun_called if mmun_start and mmun_end were
initialized and, if so, may call mmu_notifier_invalidate_range_end()
with these values. This doesn't prevent gcc from emitting a build
warning though:
mm/memory.c: In function `do_wp_page':
mm/memory.c:2530: warning: `mmun_start' may be used uninitialized in this function
mm/memory.c:2531: warning: `mmun_end' may be used uninitialized in this function
It's much easier to initialize the variables to impossible values and do
a simple comparison to determine if they were initialized to remove the
bool entirely.
Signed-off-by: David Rientjes <rientjes@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/memcontrol.c')
0 files changed, 0 insertions, 0 deletions