Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752599AbbLSBFJ (ORCPT ); Fri, 18 Dec 2015 20:05:09 -0500 Received: from userp1040.oracle.com ([156.151.31.81]:18371 "EHLO userp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751499AbbLSBFH (ORCPT ); Fri, 18 Dec 2015 20:05:07 -0500 From: Sasha Levin To: akpm@linux-foundation.org Cc: mhocko@suse.com, mgorman@suse.de, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Sasha Levin Subject: [PATCH] mm, oom: initiallize all new zap_details fields before use Date: Fri, 18 Dec 2015 20:04:51 -0500 Message-Id: <1450487091-7822-1-git-send-email-sasha.levin@oracle.com> X-Mailer: git-send-email 2.5.0 X-Source-IP: userv0022.oracle.com [156.151.31.74] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1013 Lines: 29 Commit "mm, oom: introduce oom reaper" forgot to initialize the two new fields of struct zap_details in unmap_mapping_range(). This caused using stack garbage on the call to unmap_mapping_range_tree(). Signed-off-by: Sasha Levin --- mm/memory.c | 1 + 1 file changed, 1 insertion(+) diff --git a/mm/memory.c b/mm/memory.c index 206c8cd..0e32993 100644 --- a/mm/memory.c +++ b/mm/memory.c @@ -2431,6 +2431,7 @@ void unmap_mapping_range(struct address_space *mapping, details.last_index = hba + hlen - 1; if (details.last_index < details.first_index) details.last_index = ULONG_MAX; + details.check_swap_entries = details.ignore_dirty = false; /* DAX uses i_mmap_lock to serialise file truncate vs page fault */ -- 1.7.10.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/