linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "zhangpeng (AS)" <zhangpeng362@huawei.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: "Huang, Ying" <ying.huang@intel.com>, <linux-mm@kvack.org>,
	<linux-kernel@vger.kernel.org>, <akpm@linux-foundation.org>,
	<fengwei.yin@intel.com>, <aneesh.kumar@linux.ibm.com>,
	<shy828301@gmail.com>, <hughd@google.com>, <david@redhat.com>,
	<wangkefeng.wang@huawei.com>, <sunnanyong@huawei.com>
Subject: Re: [RFC PATCH] mm: filemap: avoid unnecessary major faults in filemap_fault()
Date: Fri, 24 Nov 2023 10:04:00 +0800	[thread overview]
Message-ID: <e41dff89-9fc0-66ca-3156-9d61dbc3d92d@huawei.com> (raw)
In-Reply-To: <ZV9wt4+F/soWxVhR@casper.infradead.org>

On 2023/11/23 23:33, Matthew Wilcox wrote:

> On Thu, Nov 23, 2023 at 05:09:04PM +0800, zhangpeng (AS) wrote:
>>>> +		pte_t *ptep = pte_offset_map_lock(vmf->vma->vm_mm, vmf->pmd,
>>>> +						  vmf->address, &vmf->ptl);
>>>> +		if (ptep) {
>>>> +			/*
>>>> +			 * Recheck pte with ptl locked as the pte can be cleared
>>>> +			 * temporarily during a read/modify/write update.
>>>> +			 */
>>>> +			if (unlikely(!pte_none(ptep_get(ptep))))
>>>> +				ret = VM_FAULT_NOPAGE;
>>>> +			pte_unmap_unlock(ptep, vmf->ptl);
>>>> +			if (unlikely(ret))
>>>> +				return ret;
>>>> +		}
>>>> +
>>> Need to deal with ptep == NULL.  Although that is high impossible.
>> If ptep == NULL, we may just need to return VM_FAULT_SIGBUS.
>> I'll add it in the next version.
> no?  wouldn't ptep being NULL mean that the ptep has been replaced with
> a PMD entry, and thus should return NOPAGE?

Yes, ptep == NULL means that the ptep has been replaced with a PMD entry.
I'll add return NOPAGE in the next version.

Thanks!

-- 
Best Regards,
Peng



  reply	other threads:[~2023-11-24  2:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 14:00 Peng Zhang
2023-11-23  1:09 ` Yin Fengwei
2023-11-23  4:12   ` zhangpeng (AS)
2023-11-23  5:26     ` Yin Fengwei
2023-11-23  7:57       ` zhangpeng (AS)
2023-11-23  8:29         ` Yin Fengwei
2023-11-23  9:09           ` zhangpeng (AS)
2023-11-24  4:13         ` Huang, Ying
2023-11-24  4:26           ` Huang, Ying
2023-11-24  7:27             ` zhangpeng (AS)
2023-11-24  8:04               ` Huang, Ying
2023-11-29  1:24                 ` zhangpeng (AS)
2023-11-29  2:59                   ` Huang, Ying
2024-02-01 12:10                     ` zhangpeng (AS)
2024-02-02  0:39                       ` Huang, Ying
2024-02-02  3:31                         ` zhangpeng (AS)
2023-11-24  7:26           ` zhangpeng (AS)
2023-11-23  8:36 ` Huang, Ying
2023-11-23  9:09   ` zhangpeng (AS)
2023-11-23 15:33     ` Matthew Wilcox
2023-11-24  2:04       ` zhangpeng (AS) [this message]
2023-11-24  7:26   ` zhangpeng (AS)
2023-11-24  7:59     ` Huang, Ying
2023-11-24  6:05 ` Matthew Wilcox
2023-11-24  7:43   ` zhangpeng (AS)

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=e41dff89-9fc0-66ca-3156-9d61dbc3d92d@huawei.com \
    --to=zhangpeng362@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=fengwei.yin@intel.com \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shy828301@gmail.com \
    --cc=sunnanyong@huawei.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=willy@infradead.org \
    --cc=ying.huang@intel.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