linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wanpeng Li <liwanp@linux.vnet.ibm.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: Bob Liu <lliubbo@gmail.com>,
	Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
	Bob Liu <bob.liu@oracle.com>, Linux-MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: could you clarify mm/mempolicy: fix !vma in new_vma_page()
Date: Tue, 7 Jan 2014 12:26:13 +0800	[thread overview]
Message-ID: <52cb81ed.e3d8420a.72a1.ffffea65SMTPIN_ADDED_BROKEN@mx.google.com> (raw)
In-Reply-To: <20140106141827.GB27602@dhcp22.suse.cz>

Hi Michal,
On Mon, Jan 06, 2014 at 03:18:27PM +0100, Michal Hocko wrote:
>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?

Not just for hugetlb pages, sorry for do two things in one patch. The change 
for hugetlb pages is to fix the potential dereference NULL pointer reported 
by Dan. http://marc.info/?l=linux-mm&m=137689530323257&w=2 

If we should ask Sasha to add more debug information to dump which condition 
is failed in page_address_in_vma() for you?

Regards,
Wanpeng Li 
	

>
>-- 
>Michal Hocko
>SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2014-01-07  4:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06 11:24 Michal Hocko
2014-01-06 12:45 ` Bob Liu
2014-01-06 14:18   ` Michal Hocko
2014-01-07  4:26     ` Wanpeng Li [this message]
2014-01-07  4:34       ` Wanpeng Li
2014-01-07  8:34         ` Michal Hocko
2014-01-07  5:29     ` Bob Liu
2014-01-07 10:22       ` Michal Hocko
2014-01-07 17:30         ` Michal Hocko
2014-01-08  0:56           ` Bob Liu
2014-01-08 10:08             ` Michal Hocko
2014-01-08 12:09               ` Bob Liu
2014-01-08 12:42                 ` Michal Hocko
2014-01-08 13:10                   ` Bob Liu
2014-01-08 13:49                     ` Michal Hocko
2014-01-08 13:54                     ` Michal Hocko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52cb81ed.e3d8420a.72a1.ffffea65SMTPIN_ADDED_BROKEN@mx.google.com \
    --to=liwanp@linux.vnet.ibm.com \
    --cc=bob.liu@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lliubbo@gmail.com \
    --cc=mhocko@suse.cz \
    --cc=n-horiguchi@ah.jp.nec.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox