mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yun Zhou <yun.zhou@windriver.com>
To: Peter Xu <peterx@redhat.com>
Cc: akpm@linux-foundation.org, corbet@lwn.net,
	tiberiu.georgescu@nutanix.com, florian.schmidt@nutanix.com,
	ivan.teterevkov@nutanix.com, sj@kernel.org, shy828301@gmail.com,
	david@redhat.com, axelrasmussen@google.com, linmiaohe@huawei.com,
	aarcange@redhat.com, ccross@google.com, apopple@nvidia.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] proc: fix documentation and description of mmap
Date: Tue, 1 Mar 2022 12:39:37 +0800	[thread overview]
Message-ID: <4b23a6c4-4b69-019f-7885-d4c9f61e9503@windriver.com> (raw)
In-Reply-To: <Yh2aKofkcWsLswQm@xz-m1.local>



On 3/1/22 11:59 AM, Peter Xu wrote:
> [Please note: This e-mail is from an EXTERNAL e-mail address]
> 
> On Tue, Mar 01, 2022 at 11:21:15AM +0800, Yun Zhou wrote:
>> diff --git a/fs/proc/task_mmu.c b/fs/proc/task_mmu.c
>> index 78125ef20255..75511f78075f 100644
>> --- a/fs/proc/task_mmu.c
>> +++ b/fs/proc/task_mmu.c
>> @@ -1596,7 +1596,8 @@ static const struct mm_walk_ops pagemap_ops = {
>>    * Bits 5-54  swap offset if swapped
>>    * Bit  55    pte is soft-dirty (see Documentation/admin-guide/mm/soft-dirty.rst)
>>    * Bit  56    page exclusively mapped
>> - * Bits 57-60 zero
>> + * Bit  57    pte is uffd-wp write-protected (since 5.13) (see
>                                                  ^^^^^^^^^^^^^^^^^ remove these?
Sorry for my mistake, I will follow your suggestion and send patch v2.

Thanks,
Yun

      reply	other threads:[~2022-03-01  4:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01  3:21 Yun Zhou
2022-03-01  3:59 ` Peter Xu
2022-03-01  4:39   ` Yun Zhou [this message]

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=4b23a6c4-4b69-019f-7885-d4c9f61e9503@windriver.com \
    --to=yun.zhou@windriver.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=apopple@nvidia.com \
    --cc=axelrasmussen@google.com \
    --cc=ccross@google.com \
    --cc=corbet@lwn.net \
    --cc=david@redhat.com \
    --cc=florian.schmidt@nutanix.com \
    --cc=ivan.teterevkov@nutanix.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterx@redhat.com \
    --cc=shy828301@gmail.com \
    --cc=sj@kernel.org \
    --cc=tiberiu.georgescu@nutanix.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
all inboxes | Powered by JetHome®