Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752708AbaAFOSb (ORCPT ); Mon, 6 Jan 2014 09:18:31 -0500 Received: from cantor2.suse.de ([195.135.220.15]:39344 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750902AbaAFOSa (ORCPT ); Mon, 6 Jan 2014 09:18:30 -0500 Date: Mon, 6 Jan 2014 15:18:27 +0100 From: Michal Hocko To: Bob Liu Cc: Wanpeng Li , Naoya Horiguchi , Bob Liu , Linux-MM , LKML Subject: Re: could you clarify mm/mempolicy: fix !vma in new_vma_page() Message-ID: <20140106141827.GB27602@dhcp22.suse.cz> References: <20140106112422.GA27602@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 06-01-14 20:45:54, Bob Liu wrote: [...] > 544 if (PageAnon(page)) { > 545 struct anon_vma *page__anon_vma = page_anon_vma(page); > 546 /* > 547 * Note: swapoff's unuse_vma() is more efficient with this > 548 * check, and needs it to match anon_vma when KSM is active. > 549 */ > 550 if (!vma->anon_vma || !page__anon_vma || > 551 vma->anon_vma->root != page__anon_vma->root) > 552 return -EFAULT; > 553 } else if (page->mapping && !(vma->vm_flags & VM_NONLINEAR)) { > 554 if (!vma->vm_file || > 555 vma->vm_file->f_mapping != page->mapping) > 556 return -EFAULT; > 557 } else > 558 return -EFAULT; > > That's the "other conditions" and the reason why we can't use > BUG_ON(!vma) in new_vma_page(). Sorry, I wasn't clear with my question. I was interested in which of these triggered and why only for hugetlb pages? -- Michal Hocko SUSE Labs -- 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/