Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754644AbbDHQP7 (ORCPT ); Wed, 8 Apr 2015 12:15:59 -0400 Received: from mail-ob0-f170.google.com ([209.85.214.170]:35553 "EHLO mail-ob0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754628AbbDHQP5 (ORCPT ); Wed, 8 Apr 2015 12:15:57 -0400 Date: Wed, 8 Apr 2015 11:15:39 -0500 From: Shawn Bohrer To: linux-mm@kvack.org Cc: linux-kernel@vger.kernel.org Subject: HugePages_Rsvd leak Message-ID: <20150408161539.GA29546@sbohrermbp13-local.rgmadvisors.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1830 Lines: 43 I've noticed on a number of my systems that after shutting down my application that uses huge pages that I'm left with some pages still in HugePages_Rsvd. It is possible that I still have something using huge pages that I'm not aware of but so far my attempts to find anything using huge pages have failed. I've run some simple tests using map_hugetlb.c from the kernel source and can see that pages that have been reserved but not allocated still show up in /proc//smaps and /proc//numa_maps. Are there any cases where this is not true? [root@dev106 ~]# grep HugePages /proc/meminfo AnonHugePages: 241664 kB HugePages_Total: 512 HugePages_Free: 512 HugePages_Rsvd: 384 HugePages_Surp: 0 Hugepagesize: 2048 kB [root@dev106 ~]# grep "KernelPageSize:.*2048" /proc/*/smaps [root@dev106 ~]# grep "VmFlags:.*ht" /proc/*/smaps [root@dev106 ~]# grep huge /proc/*/numa_maps [root@dev106 ~]# grep Huge /proc/meminfo AnonHugePages: 241664 kB HugePages_Total: 512 HugePages_Free: 512 HugePages_Rsvd: 384 HugePages_Surp: 0 Hugepagesize: 2048 kB So here I have 384 pages reserved and I can't find anything that is using them. This is on a machine running 3.14.33. I can possibly try running a newer kernel if there is a belief that this has been fixed. I'm also happy to provide more information or try some debug patches if there are ideas on how to track this down. I'm not entirely sure how hard this is to reproduce but nearly every machine I've looked at is in this state so it must not be too hard. Thanks, Shawn -- 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/